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 believe it is necessary to reassess the decision of making the Bicep language fully newline insensitive in the long run. The recent fixes we implemented for specific syntax issues, such as #586 and #5829, were temporary patches that lack flexibility. While allowing newlines before the ? and : in a ternary operator is permitted, parsing errors still arise when newlines are introduced after them. This issue extends to other syntaxes such as lambdas and for-expressions, requiring additional manual patches to the parser and resulting in heightened fragility.
Although the original intention behind making Bicep newline sensitive was to simplify error recovery logic and enhance error messages, it is still possible to develop a recursive descent parser that handles a newline-insensitive grammar while providing informative error messages. However, implementing such changes could be disruptive and time-consuming. It would require careful consideration and significant effort to achieve the desired outcome.
The text was updated successfully, but these errors were encountered:
I believe it is necessary to reassess the decision of making the Bicep language fully newline insensitive in the long run. The recent fixes we implemented for specific syntax issues, such as #586 and #5829, were temporary patches that lack flexibility. While allowing newlines before the ? and : in a ternary operator is permitted, parsing errors still arise when newlines are introduced after them. This issue extends to other syntaxes such as lambdas and for-expressions, requiring additional manual patches to the parser and resulting in heightened fragility.
Although the original intention behind making Bicep newline sensitive was to simplify error recovery logic and enhance error messages, it is still possible to develop a recursive descent parser that handles a newline-insensitive grammar while providing informative error messages. However, implementing such changes could be disruptive and time-consuming. It would require careful consideration and significant effort to achieve the desired outcome.
The text was updated successfully, but these errors were encountered: