-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Shrink AST DenseMaps #23323
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
Shrink AST DenseMaps #23323
Conversation
@swift-ci please smoke test |
With luck we’ll live in a world with only “simple” paren types. LGTM |
@swift-ci Please smoke test compiler performance |
You can merge ahead of my perf tests. I just want to see if anything shows up. (By the way, Mark is no longer working on Swift these days. :-( ) |
@jrose-apple – Outside of contrived or pathological scenarios, I doubt this will impact the perf suite. It's just the right thing to do. On the topic of code review, I really wish we'd reconsider the "CODE_OWNERS.txt" proposal. It doesn't need GitHub enforcement, just up to date so that GitHub can recommend code reviewers. |
More so, as an outsider, the GitHub's attempt at guessing the "right" reviewers isn't helpful most of the time. It seems like a crude "who touched these lines last" algorithm. |
I think that's exactly what it is. Still better than nothing, but yeah, not as good as something more specified. |
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 as well!
Memory saves are generally good. Also, searching a DenseMap for a
llvm::PointerIntPair
is slightly faster than astd:pair
.