Victor Zverovich
Victor Zverovich
Item 1 now gives the same output in C++20 (https://godbolt.org/z/qhcWPer7G) and C++23 (https://godbolt.org/z/er8qzjrYx): ```c++ #include #include int main() { std::string line = "a,b-c,d-e,f"; fmt::print("{}\n", line | std::views::split(',')); } ``` Output:...
> Should fill apply to each item, or the whole? Fill should normally apply to the whole item. There are no plans to switch to a different format string syntax.
@BenFrantzDale, thanks for the suggestion but I'm not sure if `my_monostate` example adds much compared to the existing examples.
> Is this a valid format string? No because format specs should either be followed by `}` or the end of string.
It is not valid which you can easily check but formatter can be used on it's own to parse just specs which is sometimes useful.
As I wrote before: > formatter can be used on it's own to parse just specs Also you need the end check to correctly handle invalid format strings. Such strings...
The documentation has been completely revamped. In particular, it now contains some recommended practices such as how to handle fill, align and width. It also documents the new APIs such...
There is no update on the {fmt}-only solution but you can use `std::ostream` with {fmt} with the former managing buffering and low-level I/O while the latter doing the formatting.
Closing for now since this doesn't look actionable. Feel free to reopen if additional information comes up that indicates that the problem is on the {fmt} side.
Both clang 14 and gcc 12 work in https://compiler-explorer.com/z/MEn4MPq7a. Not sure what clang-cl error means but it might be due to incompatible build settings. Closing as this doesn't look actionable...