Skip to content

doc extension concerning format_as and general implementations #4857

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.

Sign up for GitHub

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
vitaut merged 3 commits into from
Jul 29, 2026
Merged

doc extension concerning format_as and general implementations #4857

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
897e394
add a sentence about the possible interaction of format_as and genera…
rimathia Jul 17, 2026
6dc7493
remove link update, doesn't seem to be necessary
rimathia Jul 17, 2026
61e3276
use much more precise statement
rimathia Jul 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions doc/api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,6 +92,10 @@ Use `format_as` if you want to make your type formattable as some other
type with the same format specifiers. The `format_as` function should
take an object of your type and return an object of a formattable type.
It should be defined in the same namespace as your type.
`format_as` cannot be used when a type also matches another `formatter`
specialization, such as the range `formatter`, because the specializations
would be ambiguous. Disable the conflicting specialization, if possible,
or provide an explicit `formatter` specialization instead.

Example ([run](https://godbolt.org/z/nvME4arz8)):

Expand Down
Loading