CppCoreGuidelines
github-cheat-sheet
Our great sponsors
CppCoreGuidelines | github-cheat-sheet | |
---|---|---|
306 | 2 | |
41,290 | 45,164 | |
0.8% | - | |
7.6 | 2.0 | |
17 days ago | 28 days ago | |
Python | ||
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
CppCoreGuidelines
- Learn Modern C++
-
Modern C++ Programming Course
You need to talk to Bjarne and Herb...
"C++ Core Guidelines" - https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines
- CLion Nova Explodes onto the C and C++ Development Scene
-
Toward a TypeScript for C++"
In addition to the other comments -
TypeScript deliberately takes a "good enough" approach to improving JavaScript, instead of designing an ideal but incompatible approach. For example, its handling of [function parameter bivariance](https://www.typescriptlang.org/docs/handbook/type-compatibil...) is unsound but works much better with the existing JavaScript ecosystem. By contrast, a more academic functional programming language would guarantee a sound type system but would be a huge shift from JavaScript.
By analogy, Herb Sutter is arguing that something like the [C++ Core Guidelines](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines), with tooling help in this new Cpp2 syntax, can bring real improvements to safety. Something like Rust's borrow checker would bring much stricter guarantees, backed by academic research and careful design, but would be incompatible and a huge adjustment.
-
C++ is everywhere, but noone really talks about it. What are people's thoughts?
Another phenomenal resource is the ISO C++ core guidelines which is essentially a giant list of best practices of newer c++ features. These guidelines were a collaborative effort started by Bjarne Stroustrup who know a bit about c++. There is an entire section about resource management if you're interested in learning more about the newer facilities c++ offers in that regard to avoid the footguns, but there is a ton of other great information in there as well.
Take a look at Effective Modern c++ by Scott Meyers and the ISO c++ core guidelines. These resources are great for learning how to write better, more modern C++. I don't think it would be hard to grasp if you're already familiar with the language, just make sure to actually write some code which makes use of this stuff, otherwise it's easy to forget.
-
What are some C++ specific antipatterns that might be missed by C#/Java devs?
Look to the C++ Core Guidelines. It's not perfect, it has some flaws, including some sabotaging advice apparently adopted for political reasons. But at least it has some C++ authorities (Bjarne and Herb) as authors.
-
How to improve the code quality
Also, tried to follow https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines as much as I could.
-
Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022
C++: Not memory safe and tons of ceremonial to avoid UB and have actually well defined objects, semantically: for example, rule of five. Needs to follow a huge number of "core guidelines", https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines, many of the most important are not automatically enforceable by tools. No enum types, invisible codepaths everywhere due to exceptions. Stupid textual-inclusion compilation model meaning that you need to manually track which headers should actually be included in a file (in particular, when reviewing changes to that file that may or may not render some header inclusions useless). Namespace system where the namespace is not inferred from the file/package, but explicitly declared in the file, meaning that name collisions are possible (and result in an ill formed program, no diagnostic required. Once had to debug a colleague's ODR violation that made even valgrind segfault... very fun afternoon) and should be watched for in review. No unsafe and anything could be UB, so have to be paranoid about everything that is being done.
github-cheat-sheet
-
Question about a github book
Not aware of a book - but what you describe sounds a little like the github cheatsheet - could it be someone turned this (or the talk mentioned in the intro) into an ebook or pdf?
-
Free 500+ books and learning resources for every programmer.
GitHub Cheat Sheet - Tim Green (Markdown)
What are some alternatives?
awesome-competitive-programming - :gem: A curated list of awesome Competitive Programming, Algorithm and Data Structure resources
devdocs - API Documentation Browser
book - The Rust Programming Language
Crafting Interpreters - Repository for the book "Crafting Interpreters"
LearnOpenGL - Code repository of all OpenGL chapters from the book and its accompanying website https://learnopengl.com
git-internals-pdf - PDF on Git Internals
Power-Fx - Power Fx low-code programming language
awesome-remote-job - A curated list of awesome remote jobs and resources. Inspired by https://github.com/vinta/awesome-python
clojure-style-guide - A community coding style guide for the Clojure programming language
too-many-lists - Learn Rust by writing Entirely Too Many linked lists
range-v3 - Range library for C++14/17/20, basis for C++20's std::ranges
awesome-eslint - A list of awesome ESLint plugins, configs, etc.