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
The immediate workaround is to place a space before the comment.
a( is parsed as a single token, unlike a (, and won't identify the beginning of a comment. We could introduce a new rule that would identify a(* as a single token and return a followed by a comment. It may break existing code that contains something like a(*) although this is discouraged in favor of a( * ). Perhaps we could produce a warning or an error message that gives a tentative solution.
Maybe the warning could appear in the a(*) case, since that's the one you're discouraging. Anyway, thanks for the suggestion, we'll just use the workaround for now.
This seems to have been caused by the parser changes in 1.3.0. Minimal repro:
a(* ( *)
Here's the error message.
The lack of a space before the opening parenthesis of the comment is significant: when added, this parses.
The text was updated successfully, but these errors were encountered: