Minimal Logging Framework in C++20 - Koen Poppe - Meeting C++ 2023

Minimal Logging Framework in C++20 - Koen Poppe - Meeting C++ 2023
Slides: slides.meeting...
Survey: survey.meeting...
As developers, adding log statements seems easy and risk-free. However, with hundreds of machines, collecting those log files can become quite a challenge, let alone making sense of the important information they contain. We set out to reduce logging to its essentials and explore optimisations not only in terms of disk space, but also runtime performance and even exposure. Leveraging ideas from well-known software related workflows, we will write a C++20 logging framework from scratch and highlight some surprises along the way.

[@pancio-ciancio]

I love the idea presented but I don't like the implementation (for no particular reason, just personal "taste").
Great talk 🙏

[@christer8964]

If the compile ignore always_inline.
Can the compiler chose to ignore just some of the calls?

[@Roibarkan]

30:28 I believe that the trivially_copyable type trait can be used to ensure that users will not try to log types where memcpy isn’t suitable

[@SerFluffikins]

Sounds right, thank you for the suggestion! I've updated the source code on GitHub accordingly.

[@adamkonrad]

It would not be something if there was no circular buffer... :/