mirror of
https://github.com/fmtlib/fmt.git
synced 2026-10-29 02:17:28 +08:00
The tuple formatter had a bespoke trait to keep format_as from producing an ambiguous specialization. detail::has_format_as already answers that question and std.h applies it the same way, so move it from std.h to format.h where ranges.h can see it and drop the extra trait. Check it with conditional_t rather than &&: is_tuple_formattable must not be instantiated for types with format_as because for self-referential tuple-like types that recurses back into formatter selection, and && short-circuits evaluation but not instantiation. |
||
|---|---|---|
| .. | ||
| fmt | ||