Victor Zverovich
Victor Zverovich
`fmt::format` is modeled after Python's `str.format` where shortest refers to the precision, not the full output. `std::format` diverged a bit because it was specified in terms of `to_chars`.
I am open to PRs to address this backed by more analysis of the effects of the change and concrete examples.
This is unrelated and I am surprised that `to_chars` produces "garbage" digits in this case.
That's the term they used in Grisu paper. You can control precision, so there is no issue here.
There is a simpler repro for the `set_debug_format` error in https://github.com/fmtlib/fmt/issues/3763#issue-2048061455.
Let's keep this one open for tracking the issue.
The `set_debug_format` issue is fixed in https://github.com/fmtlib/fmt/commit/3eb3aef5753b91d689b496a629b9dc5c4a7cd348 but looks like there is another problem.
The original repro compiles now: https://godbolt.org/z/ahh86ME13. Thanks @Arghnews for the fix!
`FMT_DEPRECATED_OSTREAM` has been removed so this conflict won't happen on the current version. You can format objects via ostream as follows: ```c++ fmt::print("{}\n", fmt::streamed(m)); ``` In this case Eigen providing...
I think you are right and we should improve the begin/end check. Could you submit a PR with your proposed fix?