Oliver SchönrockMar 9

@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
Show threadvitaut 🤍❤️🤍 🇺🇦Mar 9
@oschonrock which thing?
Show threadOliver SchönrockMar 9

@vitaut

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

watch the video.. it's only 7mins

Show threadvitaut 🤍❤️🤍 🇺🇦Mar 9
@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
Show threadOliver SchönrockMar 9

@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.

Show threadvitaut 🤍❤️🤍 🇺🇦Mar 9
@oschonrock They are all aware. The problems is that WG21 has been dumping tons of garbage and the number of maintainers is very low.
Show threadvitaut 🤍❤️🤍 🇺🇦
@oschonrock It might be sufficient for one implementation to do it correctly and the others will be shamed into doing the same.
Mar 9 at 9:11pmMastodon for iOS