-
Notifications
You must be signed in to change notification settings - Fork 82
Debugging experience for patterns needs a cleanup #1974
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
Comments
@bkonyi Are there any expectations for how stepping through patterns like this works when debugging on the VM? |
I'm not sure what the behavior will be like as it depends on where we insert breakpoints into generated code. Maybe @alexmarkov will have a better idea or know who will? |
Debugger behavior depends on how patterns are lowered in the front-end and how source positions are assigned to the AST nodes. However, VM has a logic to avoid stopping at the same position repeatedly: So even if there are many AST nodes with the same source position, VM would stop at the first one and then skip the rest of the stops, until the source position changes. |
Looking at the screenshot, there are a few initial questions that come to my mind.
I don't expect these all to be answered already but I'd like to get the discussion started and I'm not sure who should be involved. |
I am going to split this into a few things:
|
All done! |
Stepping into the statement on the breakpoint line seems to stuck forever on the same spot
Compiler-generated locals appear in the variables window
The text was updated successfully, but these errors were encountered: