We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This topic pops up from time to time. Sometimes, we have to annotate operators, e.g., with types or the sets of assigned variables, #226 and #261.
It looks to me that annotating expressions is a too fine-grained approach. On the other hand, we can annotate operator definitions. I see two options:
TlaOperDecl
TlaEx
uid
I think the second approach is more flexible and extendable, but we will have to extend TransformationListener.
TransformationListener
@Kukovec what is your opinion?
The text was updated successfully, but these errors were encountered:
Duplicate of #262
Sorry, something went wrong.
konnov
No branches or pull requests
This topic pops up from time to time. Sometimes, we have to annotate operators, e.g., with types or the sets of assigned variables, #226 and #261.
It looks to me that annotating expressions is a too fine-grained approach. On the other hand, we can annotate operator definitions. I see two options:
TlaOperDecl
,TlaEx
, introduce a uid inTlaOperDecl
and store annotations as maps fromuid
to whatever.I think the second approach is more flexible and extendable, but we will have to extend
TransformationListener
.@Kukovec what is your opinion?
The text was updated successfully, but these errors were encountered: