-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Matcher does not support variables on the RHS of an operation #32
Labels
Comments
brett19
added a commit
to brett19/gojsonsm
that referenced
this issue
Aug 3, 2018
…late after nodes correctly. In a number of different cases, the compiler was incapable of figuring out the correct place for after nodes. This also made it impossible for there to be fields on the RHS of an expression as the compiler would get confused and incorrectly compile them.
brett19
added a commit
that referenced
this issue
Aug 9, 2018
In a number of different cases, the compiler was incapable of figuring out the correct place for after nodes. This also made it impossible for there to be fields on the RHS of an expression as the compiler would get confused and incorrectly compile them.
I think this bug is no longer the case and could be closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While the Transformer generates the correct output for this case, the Matcher will then panic if it sees any variables access on the RHS...
The text was updated successfully, but these errors were encountered: