The C++ Core Guidelines are a set of tried-and-true guidelines, rules, and best practices about coding in C++ (by isocpp)

CppCoreGuidelines Alternatives

Similar projects and alternatives to CppCoreGuidelines

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better CppCoreGuidelines alternative or higher similarity.

CppCoreGuidelines reviews and mentions

Posts with mentions or reviews of CppCoreGuidelines. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-11-28.
  • Modern C++ Programming Course
    5 projects | news.ycombinator.com | 28 Nov 2023
    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
    4 projects | news.ycombinator.com | 9 Nov 2023
  • Toward a TypeScript for C++"
    8 projects | news.ycombinator.com | 4 Nov 2023
    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?
    8 projects | /r/cscareerquestions | 8 Jul 2023
    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.
    8 projects | /r/cscareerquestions | 8 Jul 2023
    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?
    3 projects | /r/cpp_questions | 29 Jun 2023
    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
    4 projects | /r/cpp | 29 Jun 2023
    Also, tried to follow https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines as much as I could.
    4 projects | /r/cpp | 29 Jun 2023
  • Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022
    5 projects | /r/rust | 27 Jun 2023
    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.
  • #pragma once vs #ifndef
    2 projects | /r/cpp | 19 Jun 2023
  • A note from our sponsor - InfluxDB
    www.influxdata.com | 30 Nov 2023
    Manage all types of time series data in a single, purpose-built database. Run at any scale in any environment in the cloud, on-premises, or at the edge. Learn more →


Basic CppCoreGuidelines repo stats
26 days ago
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives