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 think what is happening is that "Subtree1" is first reading from test_port as an int, whereas "Subtree2" is then reading from test_port as a void-typed port. Switching the order so that "Subtree2" is invoked before "Subtree1" does not reproduce the exception.
Should this really throw an exception? Should we not throw this exception if the port isn't changing to a void type?
The text was updated successfully, but these errors were encountered:
The full exception that is thrown is
Here is an example tree that reproduces this issue:
I think what is happening is that "Subtree1" is first reading from test_port as an int, whereas "Subtree2" is then reading from test_port as a void-typed port. Switching the order so that "Subtree2" is invoked before "Subtree1" does not reproduce the exception.
Should this really throw an exception? Should we not throw this exception if the port isn't changing to a void type?
The text was updated successfully, but these errors were encountered: