Readit Newsvitaut commented on Stdio(3) change: FILE is now opaque undeadly.org/cgi?action=a... · Posted by u/gslin
However, who should really rely on internals of FILE? Isn't this a bad practice?
In general, it is a bad practice. However, it can be useful for some low-level libraries. For example, https://github.com/fmtlib/fmt provides a type-safe replacement for `printf` that can write directly to the FILE buffer providing comparable or better performance to native stdio.
vitaut commented on Initialization in C++ is bonkers (2017) blog.tartanllama.xyz/init... · Posted by u/todsacerdoti
vitaut commented on Stuffed-Na(a)N: stuff your NaNs github.com/si14/stuffed-n... · Posted by u/dgroshev
I made a garlic nan: https://www.godbolt.org/z/enjv1c7Tf
vitaut commented on C++26: more constexpr in the core language sandordargo.com/blog/2025... · Posted by u/jandeboevrie
C++23 doesn't have full reflection yet. That's coming in C++26.
I've seen the vast majority of build time in a very large C++23 project be taken up by reflection in fmtlib and magic_enum because both have to use templates (I think).
{fmt} doesn't use reflection and is optimized for build speed using type erasure: https://vitaut.net/posts/2024/faster-cpp-compile-times/
I'm curious to take a closer look at fmtlib/fmt, which APIs treat FILE as non-opaque?
Edit: ah, found some of the magic, I think: https://github.com/fmtlib/fmt/blob/35dcc58263d6b55419a5932bd...
I'm curious how much speedup is gained from this.