Victor Zverovich
Victor Zverovich
In theory yes but I wouldn't recommend it. None of the standard formatters do this.
Format string parsing is indeed not exposed in the public API at the moment.
> a different format specifier to indicate preference of std::num_put instead of std::numpunct is probably a bad idea. It is. As Jonathan correctly pointed out `wchar_t` doesn't solve the problem...
{fmt} now supports the UTF-8 `format_facet` locale facet which, among other things, makes using multi-code-unit digit separators possible. For example: ```c++ #include #include int main() { std::locale::global(std::locale({}, new fmt::format_facet("’"))); fmt::print("{:L}\n",...
This is surprising because `vector` doesn't need to be convertible to `string_view` to be formattable as a range of chars. See e.g. https://godbolt.org/z/4oPK6dxM5.
I don't have a windows machine at hand and the issue doesn't repro on godbolt. If someone is able to repro and can investigate this issue it would be appreciated.
Thanks for investigating, @strega-nil-ms. Does https://github.com/fmtlib/fmt/commit/e4f4fc77884196163b45b528875bf65d1c9b922e fix the issue?
> the different parameter ordering of is_constructible and is_convertible Ugh. Thanks!
Should be fixed in https://github.com/fmtlib/fmt/commit/4a8e2949bb8d803a7607b62b632ec6d8669b7995.
Fixed in #3037 but we might want to patch released docs.