-
Notifications
You must be signed in to change notification settings - Fork 831
Dive into types in type test expressions in AST visitor traverse #5951
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
Conversation
|
Is it possible to add a test case for this? |
7428ef8 to
343ed6d
Compare
|
@TIHan Thanks, I added a test. |
343ed6d to
db7cf44
Compare
db7cf44 to
1130a55
Compare
TIHan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Seems CI is still failing though. When that is resolved, we can merge.
|
Also, as a note, I am also lurking in changing some of this code to accomodate |
|
It's green. |
|
@auduchinok Is there an issue to link here? No worries if there's no, I just want to associate something with a milestone for traceability. |
|
@cartermp No issue to link to, sorry. I pushed the fix right after discovering it. |
|
Thank you |
Currently
AstTraversal.Traversegoes intoexprparts of type test expressions only and ignorestypeparts. This PR adds diving intotypeparts.In the example below
System.Stringwill now be visited byVisitType.