Avoid stepping through ANTLR generated code when debugging (C#) #2833
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi, |
|
I see the point, maybe setting the attribute at class level is a too general. My use-case is debugging post-parsing code with custom listeners: I just don't want to go through each "XXXContext.Accept()" and "BaseVisitor.VisitXXX()" methods. I can revise my changes for the parser part and apply the DebuggerStepThrough attribute only for "Accept()" methods. Would that seem more legitimate? |
|
DebuggerNonUserCodeAttribute would be more acceptable |
ericvergnaud
approved these changes
Jun 6, 2020
|
@parrt blessed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.