You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm talking about autowrap based on PyD in this case. And I suggest we enable we can specify identifier name for aggregate being wrapped.
Here is an example. We need to wrap a type which is a template.
template struct S(T)
{
T value;
}
wrapAggregate(S!A);
wrapAggregate(S!B);
This will end with both instance in Python has same python name which is "S" and cause confliction.
I have checked the PyD implementation. PyD function wrap_class can take optional parameter PyName!"FooBar". Maybe we can dispose this to autowrap as well using optional parameters?
The text was updated successfully, but these errors were encountered:
I'm talking about autowrap based on PyD in this case. And I suggest we enable we can specify identifier name for aggregate being wrapped.
Here is an example. We need to wrap a type which is a template.
This will end with both instance in Python has same python name which is "S" and cause confliction.
I have checked the PyD implementation. PyD function wrap_class can take optional parameter PyName!"FooBar". Maybe we can dispose this to autowrap as well using optional parameters?
The text was updated successfully, but these errors were encountered: