[Bug libstdc++/113500] New: Using std::format with float or double based std::chrono::time_point causes error: no match for 'operator<<'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500 Bug ID: 113500 Summary: Using std::format with float or double based std::chrono::time_point causes error: no match for 'operator<<' Product: gcc Version: 13.1.0

[Bug libstdc++/113500] Using std::format with float or double based std::chrono::time_point causes error: no match for 'operator<<'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500 --- Comment #3 from hirtham...@allterra-dno.de --- Sorry, for the missing includes. > Since this is a bug in libstdc++ headers it's not at all surprising that you > get > the same error with any compiler using those headers. This should not ha

[Bug libstdc++/113500] Using std::format with float or double based std::chrono::time_point causes error: no match for 'operator<<'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500 --- Comment #5 from hirtham...@allterra-dno.de --- (In reply to Jonathan Wakely from comment #4) > MSVC rejects this the same way, although libc++ from LLVM 17 compiles it. > > AFAICT std::format("{}", tp) would be invalid because that formats t

[Bug libstdc++/113500] Using std::format with float or double based std::chrono::time_point causes error: no match for 'operator<<'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500 --- Comment #11 from hirtham...@allterra-dno.de --- (In reply to Jonathan Wakely from comment #7) > (In reply to Jonathan Wakely from comment #6) > > (In reply to Hirthammer from comment #5) > > > This whole thing with std::format and std::chrono