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
So does using a ":" instead of "=>". Additionally, when a colon is used, a newline does not cause an error.
$$A //= (b : [+int])
Or:
$$A //= (b :
[+int])
It looks to me that the issue is in whitespace handling where => is used. Adding the following at line 2606 in parser.rs fixes the issue for me. This is similar to whitespace handling for the colon case a few lines below 2606. I have not tested without the ast-comments feature enabled.
I was failing to validate a large CDDL file that looked like it ought work and distilled the issue down to this pattern:
The resulting error for the above was this:
However, removing the new line clears the error.
So does using a ":" instead of "=>". Additionally, when a colon is used, a newline does not cause an error.
Or:
It looks to me that the issue is in whitespace handling where => is used. Adding the following at line 2606 in parser.rs fixes the issue for me. This is similar to whitespace handling for the colon case a few lines below 2606. I have not tested without the ast-comments feature enabled.
The text was updated successfully, but these errors were encountered: