If you Google "modern c++" you will probably find ~c++11 tutorials and posts and less and less content on the latest c++ standards where some things considered "modern" a few years ago are already deprecated or not considered "best practices" anymore.
I'd check this[0] excellent mega rant about c++ and take the best parts to create a truly "contemporary c++" cheatsheet.
Thank you for sharing this excellent resource! You make a great point—searching for "modern C++" often surfaces C++11-era content, while newer standards have already deprecated some of those "modern" practices. That's exactly why I created this project: to continuously update and document contemporary best practices as the language evolves. I'll definitely check out the linked rant for ideas to incorporate. Thanks for the suggestion!
I haven't searched much, but failed to find anything related to bounds checking, or enabling hardned runtimes for C++, which I consider a must-have in any modern project.
Also probably something similar for C, like using SDS (https://github.com/antirez/sds) instead of standard library calls.
If you Google "modern c++" you will probably find ~c++11 tutorials and posts and less and less content on the latest c++ standards where some things considered "modern" a few years ago are already deprecated or not considered "best practices" anymore.
I'd check this[0] excellent mega rant about c++ and take the best parts to create a truly "contemporary c++" cheatsheet.
[0] https://youtu.be/7fGB-hjc2Gc?si=4bk2nKx2AXPYLJH7
Thank you for sharing this excellent resource! You make a great point—searching for "modern C++" often surfaces C++11-era content, while newer standards have already deprecated some of those "modern" practices. That's exactly why I created this project: to continuously update and document contemporary best practices as the language evolves. I'll definitely check out the linked rant for ideas to incorporate. Thanks for the suggestion!
I haven't searched much, but failed to find anything related to bounds checking, or enabling hardned runtimes for C++, which I consider a must-have in any modern project.
Also probably something similar for C, like using SDS (https://github.com/antirez/sds) instead of standard library calls.
Other than that, great work.
Thanks. This is a awesome suggestion. Will dive deep what is the better way to do.
This is cool, but I usually expect a cheat sheet to be a 1 or 2 page pdf.
This isn't a cheat sheet. It's a guide.