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.
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
Rework some code logic to reduce iterator and comparator inlining to improve compile time #12900
Rework some code logic to reduce iterator and comparator inlining to improve compile time #12900
Changes from 29 commits
bd63a2b
1446e08
8da8470
bcc2a14
2453e7d
edd2583
993c36d
47f1332
fb50223
8cdf813
29601dd
b842763
2a7f2de
b77db9d
f8fe035
76445b7
9c5ee0c
4cca497
3ccd0a4
f994e53
321c4d4
7f8ed2c
0370e24
5748ad8
76f48da
9c3b473
e4b7c8e
6784431
25912ca
7868b0e
69da72a
2a4f7de
c5870e9
03e8835
c142598
00f5130
52f8c29
80803a1
5089cfe
bfdf963
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
If this compiles faster for nested types, does it also compile faster for non-nested types? If it's possible to unify these and have a single implementation of the algorithms, I would prefer that (rather than one
transform + copy_if
for nested types and oneunique_copy
for non-nested types).If there are considerations like runtime, memory usage, etc. that warrant two separate implementations, then let's inform the reader with some comments explaining this decision.
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.
It does compile faster for non-nested types but the performance impact was too large (20-50% increase) for this path.