Skip to content
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

[BUG] Use of RustEqualExpression in destructuring of match statement #2

Open
simonegazza opened this issue Oct 6, 2022 · 0 comments
Assignees
Labels
bug Something isn't working enhancement New feature or request

Comments

@simonegazza
Copy link
Collaborator

Description
During match statement we use the RustEqualExpression operator (== operator). We should check if this is the right operator to use, and if not we should change it / create a new one to use. We should keep in mind that this is a destructuring operator.

Suggested implementation
It is highly recommended that we create a new node that is capable of doing destructuring and correctly evaluates the guard.

@simonegazza simonegazza added bug Something isn't working enhancement New feature or request labels Oct 6, 2022
@simonegazza simonegazza self-assigned this Oct 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant