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
We currently go without curly braces known from GPPLs in the response language since the end of a block is clear in our syntax due to the language design, except for Xtend code blocks.
For developers, it seems to be natural to have blocks enclosed with curly braces, as the range of a block can be recognized more quickly.
We should add curly braces to surround all blocks in the response language, e.g. match, effect etc.
The text was updated successfully, but these errors were encountered:
We currently go without curly braces known from GPPLs in the response language since the end of a block is clear in our syntax due to the language design, except for Xtend code blocks.
For developers, it seems to be natural to have blocks enclosed with curly braces, as the range of a block can be recognized more quickly.
We should add curly braces to surround all blocks in the response language, e.g. match, effect etc.
The text was updated successfully, but these errors were encountered: