-
Notifications
You must be signed in to change notification settings - Fork 1.6k
<format>: std::format should work for volatile arguments
#2443
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
Closed
Closed
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
ad0da14
format should work for volatile arguments
fsb4000 4fb5837
Merge branch 'main' into fix2427
fsb4000 98a6174
cannot use memcpy with volatile types
fsb4000 12bf147
clang-format
fsb4000 5ae810a
more precise comment
fsb4000 096603d
add static assert
fsb4000 16897f4
Merge branch 'main' into fix2427 and fix conflicts
fsb4000 186a121
_Phony_basic_format_arg_constructor can work with volatile types
fsb4000 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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
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.
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.
While video reviewing this, @barcharcraz and @CaseyCarter helped me understand the history of this code and what the Standard says. After looking at this, we believe that
volatile intis required to be ill-formed by the Standard, according to https://eel.is/c++draft/format.arg#4 . Specifically,will pass
declval<volatile int&>()toformatter_type<int>, and that will attempt to bind.format()'s parameterconst int&to the lvalue argument of typevolatile int, and that is not allowed.@barcharcraz says that after #2323, the example in #2427 will be accepted (with a technically-undefined memcpying from
volatile), but the Standard says we should reject this, so the code needs to be changed. I'm not immediately sure what the best change would be, butstatic_assert(!is_volatile_v<remove_reference_t<_Ty>>)(warning: not compiled, I just typed that out) might be a minimal fix. @barcharcraz and @CaseyCarter can help investigate.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.
While it doesn't require library-defined
formatterspecializations to do so, I think the wording may allow a program-definedformatterspecialization to acceptvolatilearguments. The stripping of volatile in [format.arg]/17.2 suggests to me that the drafters probably just didn't care enough to allow or forbid volatile.