@vitaut

Jason talked about THE THING....

https://www.youtube.com/watch?v=TreruByxQWE

What was the "forward declare" trick? You had a blog article about that?

You may wish to comment under Jason's video and even get him to make a video about the workaround.

And we should pressure the Vendors to improve their QoI, IMHO.

C++ Weekly - Ep 523 - Why I'm Still Using std::cout (on this channel)

YouTube
@oschonrock which thing?

@vitaut

compile time and binary size of the stdlib implementations of format and print.

watch the video.. it's only 7mins

@oschonrock That's a known problem, I even opened an issue: https://github.com/llvm/llvm-project/issues/163002. I would suggest using {fmt} until it is fixed.
Massive binary bloat in std::print 路 Issue #163002 路 llvm/llvm-project

Consider the following trivial program (std-print.cc): #include <print> int main() { std::print("{}\n", 42); } Compiling it with libc++ and Apple clang version 17.0.0 (clang-1700.3.19.1) on macOS r...

GitHub

@vitaut

yes, I am aware.

I just thought Jason covering it, would be good opportunity to broaden awareness of the real cause of the issue (QoI) and that we can hopefully expect improvements.

stdlibc++ needs to follow suit...
waiting for MSVC might take a long time.

@oschonrock @vitaut

C'mon Oliver, you can do better and check the facts first:

https://godbolt.org/z/aszhcjcPe

Compiler Explorer - C++

auto main() -> int { std::print("Hello world!"); }

@DanielaKEngert @oschonrock Microsoft STL actually implemented it correctly, nice!
@DanielaKEngert @oschonrock Actually Microsoft STL has the same problem so the difference is just a CE artefact: https://github.com/microsoft/STL/blob/26b7ca58ee3151c81736088e554e5797cafca641/stl/inc/format#L3041
STL/stl/inc/format at 26b7ca58ee3151c81736088e554e5797cafca641 路 microsoft/STL

MSVC's implementation of the C++ Standard Library. - microsoft/STL

GitHub