-
Notifications
You must be signed in to change notification settings - Fork 13
makes most operators hidden friends #471
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
Merged
Merged
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
This ensures that they're not placed in their function names' respecitve overload sets, which has a considerable impact on build times and on compiler diagnostics (as they're not listed as failed candidates when overload resolution fails).
Running an include tracer indicated that placing `size_hint_impl.h` in this header should prevent link-time errors when attempting to incidentally format `SizeHint`.
c8fe86b
to
438c023
Compare
danakj
reviewed
May 7, 2025
danakj
approved these changes
May 23, 2025
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, thanks!
Comment on lines
+64
to
+73
/// The `U` template type parameter allows `_sus_format_to_stream` to be a | ||
/// hidden friend when `Type` is not a class template. Directly using `Type` | ||
/// means that the function is immediately instantiated, and we'll get a | ||
/// compile-time error unless `fmt::formatter` is specialised before `Type`'s | ||
/// definition, since `fmt::is_formattable` doesn't know it's a formattable type | ||
/// at this point in the code. This isn't a problem for primary class templates, | ||
/// but it is problematic for regular classes and full specialisations. Using a | ||
/// dependent type `U` defers instantiation until `operator<<` is first used. | ||
/// We need to constrain `U` to be the same type as `Type`, otherwise it will | ||
/// be ambiguous as to which overload we want. |
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.
This is some wild and wonderful compiler hijacking lol. Thanks for explaining it well.
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.
This ensures that they're not placed in their function names' respective overload sets, which has a considerable impact on build times and on compiler diagnostics (as they're not listed as failed candidates when overload resolution fails).