Andre Weissflog

https://mastodon.gamedev.place/@floooh

https://twitter.com/FlohOfWoe
https://github.com/floooh/

Public Key

npub1f46780ut3dxjuz2uqlrerzpwgalj0r5ugrmmcjrfdnv3e4u8wtusa3et4e

NIP-05 Address

floooh_at_mastodon.gamedev.place@momostr.pink

Profile Code

nprofile1qqsy6a0rh79cknfwp9wq03u33qhywle836wypaaufp5kekgu67rh97gpauywc

Author Public Key

npub1f46780ut3dxjuz2uqlrerzpwgalj0r5ugrmmcjrfdnv3e4u8wtusa3et4e

Show more details

Last Notes

2024-06-08 10:09:59

- reply

just std::vector alone pulls in nearly 25kloc into each compilation unit for no good reason:
https://www.godbolt.org/z/T33jWsM6q
For reference, that's more than an entire 3D API wrapper that covers D3D11, Metal and GL:
https://github.com/floooh/sokol/blob/master/sokol_gfx.h

2024-06-08 10:04:16

- reply

for containers I would definitely write my own highly specialized classes in perf-critical code bases. Since the requirements are much more focused those can be done in a couple of hundred lines instead of tens of thousands like the stdlib containers.

2024-06-08 10:02:09

- reply

I think the Orthodox C++ advice of "don't use anything from the STL that allocates memory" makes sense for perf-critical code bases: https://gist.github.com/bkaradzic/2e39896bc7d8c34e042b
For the rare case where I use C++ for cmdline tools I'm more "open" (e.g. in sokol-shdc I use std::vector and std::string together with pystring and libfmt) but that's about as far as I would go.