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

Incorrect opcode span generated for assertions #3175

Open
TomAFrench opened this issue Oct 16, 2023 · 0 comments
Open

Incorrect opcode span generated for assertions #3175

TomAFrench opened this issue Oct 16, 2023 · 0 comments
Labels
bug Something isn't working parser issues primarily related to the parser

Comments

@TomAFrench
Copy link
Member

Aim

Noticed this while testing #3174, but it's unrelated to the changes in that PR.

I'd like to be able to go from opcodes back to the relevant expressions in Noir source code when debugging but I'm getting incorrect source being hightlighted.

Expected Behavior

I would expect the entirety of assert(x == z); to be hightlighted for the EXPR [ (-1, _3) (1, _11) 0 ] opcode.

Bug

image

To Reproduce

Installation Method

None

Nargo Version

No response

Additional Context

No response

Would you like to submit a PR for this Issue?

No

Support Needs

No response

@TomAFrench TomAFrench added the bug Something isn't working label Oct 16, 2023
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Noir Oct 16, 2023
@TomAFrench TomAFrench added the parser issues primarily related to the parser label Oct 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working parser issues primarily related to the parser
Projects
Status: 📋 Backlog
Development

Successfully merging a pull request may close this issue.

1 participant