-
Notifications
You must be signed in to change notification settings - Fork 1.7k
C++: Support printing of global and namespace variables in PrintAST
#13775
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
74ebdae
to
e69bec1
Compare
A configuration should always exist, because it does not have a charpred that could prevent this.
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.
One small comment, but otherwise this LGTM!
Also: I assume you tried this locally and double checked the that performance is fine on a non-trivial database? I remember we've had issues in the past with these VSCode-related queries not being tested on DCA and not noticing a join-order issue. |
Good point. I tried this on one file in one database, but maybe I should do a bit more extensive testing. Do you have any suggestions for a database/files on which I should try this? |
If I were to point to a really evil file I'd point you to https://raw.githubusercontent.com/wireshark/wireshark/master/epan/dissectors/packet-rrc.c (which exists in the Wireshark DB you can download from DCA) 😄. |
Either with and without the change VSCode is not able to render the file:
The time it takes to get to that point is roughly similar |
Ah, yes. That's a VSCode issue I guess 😭 |
I've tried this on some other files in the same Wireshark directory. The speed doesn't seem to have changed significantly on those files. |
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.
LGTM!
Also rename
shouldPrintFunction
toshouldPrintDeclaration
, as an initial step towards this.