-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Representation of null messages #643
Comments
Maybe I misremember that, but I think we had it like that in the past (or considered that option) and there was a reason to have the special handling. Getting rid of that would indeed be good! |
Yes there was a specific reason to do it like this although I can't remember what it was. |
Null messages are currently represented by an empty structure in
AbstractMessage
. This leads to special handling in some cases. For example ingraph
andpyrflx.typevalue
:Representing a null message by a structure of a single link from INITIAL to FINAL could make these special cases unnecessary.
The text was updated successfully, but these errors were encountered: