The C++20 Naughty and Nice List for Game Devs

Re:The C++20 Naughty and Nice List for Game Devs by tubs on Monday December 25, 2023 @03:26PM (#38765802)

In my experience if you're doing perf critical stuff with string formatting you won't be using anything like fmt or printf, and for everything else the runtime difference is almost entirely unimportant.

[ Parent | on HN ]

Re:The C++20 Naughty and Nice List for Game Devs by vitaut on Tuesday December 26, 2023 @08:03PM (#38777875)

{fmt} is commonly used for performance critical code because it provides some of the fastest numeric formatting and I/O:

* https://vitaut.net/posts/2020/fast-int-to-string-revisited/ * https://github.com/fmtlib/fmt/pull/1882 * https://vitaut.net/posts/2020/optimal-file-buffer-size/

Here's just one example: https://aras-p.info/blog/2022/02/03/Speeding-up-Blender-.obj...

[ Parent | on HN ]

Re:The C++20 Naughty and Nice List for Game Devs by tubs on Wednesday December 27, 2023 @09:44AM (#38782389)

Of that blog post the float formatting is a tiny fraction (excuse the pun) of the perf win.

[ Parent | on HN ]

Re:The C++20 Naughty and Nice List for Game Devs by vitaut on Wednesday December 27, 2023 @11:37AM (#38783644)

It's just one example showing a decent win with minimal efforts. {fmt} is widely used for getting better perf in formatted code.

[ Parent | on HN ]