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, to perform an effect on a given label, we write effect {label = l} x / r => .... This is not the best notation, because {label = l} is not a binder, but it is used in a place when a binder is expected. We agreed on a better syntax: l.effect x / r => .... Therefore, We have to change the parser.
The text was updated successfully, but these errors were encountered:
The parser is updated to match the new version of Surface. Miscellanous
syntax changes requested in existing issues or discussed elsewhere were
made too:
* #156 method definitions no longer treat self in a special way, but
the tests were not updated;
* #173;
* effect variable naming near the `handle` construct uses `/`;
* no more rows and `effect` or `label` fields (but the keyword `label`
still cannot be used as an identifier).
The tests and examples should mostly parse now, though not necessarily
as expected due to the changes to method definitions.
The parser is updated to match the new version of Surface. Miscellaneous
syntax changes requested in existing issues or discussed elsewhere were
made too:
* #156 method definitions no longer treat self in a special way, but
the tests were not updated;
* #173;
* effect variable naming near the `handle` construct uses `/`;
* no more rows and `effect` or `label` fields (but the keyword `label`
still cannot be used as an identifier).
The tests and examples should mostly parse now, though not necessarily
as expected due to the changes to method definitions.
Currently, to perform an effect on a given label, we write
effect {label = l} x / r => ...
. This is not the best notation, because{label = l}
is not a binder, but it is used in a place when a binder is expected. We agreed on a better syntax:l.effect x / r => ...
. Therefore, We have to change the parser.The text was updated successfully, but these errors were encountered: