Adam Sawicki

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

Developer Technology Engineer @ AMD. Previously @ Intel, Microsoft, gamedev, television... All opinions are my own and do not reflect that of my employer.

Homepage: https://asawicki.info/
Twitter: https://twitter.com/Reg__
LinkedIn: https://www.linkedin.com/in/adamsawicki/

Public Key

npub1v7vmdlyv7gs2rjkj2d8jfsga8sl6gxgf3rgge6yam8g5xzestesqtn7f46

NIP-05 Address

reg_at_mastodon.gamedev.place@momostr.pink

Profile Code

nprofile1qqsx0xdkljx0yg9petf9xneycywnc0ayryyc35yvazwan52rpvc9ucqpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgkwaehxw309aex2mrp0yhxummnw3ezucnpdejqamagh0

Publishing to

relay.primal.net

relay.nostr.band

Author Public Key

npub1v7vmdlyv7gs2rjkj2d8jfsga8sl6gxgf3rgge6yam8g5xzestesqtn7f46

Show more details

Last Notes

2024-06-10 08:38:31

- reply

I am not a C++ RAII purist, but in my personal code I do use unique_ptr (for single objects) and std::vector (for dynamic arrays) everywhere. I never call `new` or `delete` explicitly. I believe it gives a lot of Rust-like safety and convenience in memory management.

2024-06-10 08:38:31

- reply

2024-06-08 09:32:01

- reply

I personally like it. Some parts of it are very useful like unique_ptr, vector. I just avoid the containers that dynamically allocate every element like list, map - unless they fit to the specific problem.
I consider the fact that everyone (at least in gamedev) reimplements their own strings, containers, and everything one of the biggest issues with the C++ language, or rather - its users. It doesn't happen with other languages.

2024-06-08 09:32:01

- reply