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
Currently the interface parser has a lot of special conditions for Vector and Matrix types.
For example, in type.py, we check if the type is a Matrix or Vector type and always add a const qualifier as well as a & type.
One case where this is problematic is if we have an argument std::vector<Matrix>& which the parser converts to std::vector<const Matrix&>& which then fails compilation.
Should we drop this special behavior in favor of providing that control to the writer of the .i file? It is a bit more work for the end-user but gives them a lot more flexibility while being more transparent in case of failure.
The good news is that this change would NOT be API breaking since the change is opaque to downstream code.
The text was updated successfully, but these errors were encountered:
Currently the interface parser has a lot of special conditions for
Vector
andMatrix
types.For example, in
type.py
, we check if the type is a Matrix or Vector type and always add aconst
qualifier as well as a&
type.One case where this is problematic is if we have an argument
std::vector<Matrix>&
which the parser converts tostd::vector<const Matrix&>&
which then fails compilation.Should we drop this special behavior in favor of providing that control to the writer of the
.i
file? It is a bit more work for the end-user but gives them a lot more flexibility while being more transparent in case of failure.The good news is that this change would NOT be API breaking since the change is opaque to downstream code.
The text was updated successfully, but these errors were encountered: