SaaSHub helps you find the best software and product alternatives Learn more →
CppCoreGuidelines Alternatives
Similar projects and alternatives to CppCoreGuidelines
-
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
adventofcode
Advent of Code solutions of 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022 and 2023 in Scala (by sim642)
-
-
LearnOpenGL
Code repository of all OpenGL chapters from the book and its accompanying website https://learnopengl.com
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
carbon-lang
Carbon Language's main repository: documents, design, implementation, and related tools. (NOTE: Carbon Language is experimental; see README)
-
-
-
-
-
-
-
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
CppCoreGuidelines discussion
CppCoreGuidelines reviews and mentions
-
Don't defer Close() on writable files
> close a file (which ironically is the poster child for RAII)
Yes, I call this "RAII is a lie" (T-shirt pending).
Closing file descriptors is univerally used to showcase RAII, but it should never be used for that.
C++ has the same problem:
https://github.com/isocpp/CppCoreGuidelines/issues/2203
In there, it is acknowledged that a manual Close() should always be provided, and used if you want guarantees.
> is a bad pattern
Good that Rust at least figured it out early that it's a bad pattern!
Never use RAII in situations where the cleanup can fail!
- CppCoreGuidelines: Essential Rules and Best Practices for C++ Developers
-
What to do if you don't want a default constructor?
The standard library types are guaranteed to be in a useful state after being moved from (the term "valid state" is used for this). Of course, that doesn't mean that your own types have to, but the C++ Core Guidelines suggest doing so [1].
1: https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines...
-
I Have No Constructor, and I Must Initialize
It’s in the cpp core guidelines: https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines...
std::reference_wrapper still can’t save you from yourself, but its slightly better.
-
Fixing a memory leak of xmlEntityPtr in librsvg
Slightly tongue in cheek answer: it is easy to write this kind of code in C++ without having C involved, hence style guides will usually have a prominent guideline specifically against this type of code[1].
In Rust, I think you only really run into this issue when interacting with C (or otherwise engaging in unsafe code), so for normal Rust coding it doesn't need to be spelled out as a guideline. And the Rustonomicon[2], the go-to resource for unsafe Rust, isn't really written as a set of guidelines. At least from a brief search, I found it harder to find a Rust page that specifically says "don't do this".
1: E.g. https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines..., the first guideline in the "resource management" section.
2: https://doc.rust-lang.org/nomicon/intro.html
- Zig vs. Rust at work: the choice we made
- C++ Core Guidelines
-
Are We Modules Yet?
If you aren't aware of the c++ core guidelines[1] - it should be on your radar.
Also, it might not be a popular opinion, but I think Bjarne's books are just fine.
A Tour of C++ (3rd edition) [2]
Principles and Practice Using C++ (3rd Edition) was just published in april 2023 [3]
[1] https://github.com/isocpp/CppCoreGuidelines/blob/master/CppC...
- Learn Modern C++
-
A note from our sponsor - SaaSHub
www.saashub.com | 13 Nov 2024
Stats
isocpp/CppCoreGuidelines is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of CppCoreGuidelines is CSS.
Popular Comparisons
- CppCoreGuidelines VS Crafting Interpreters
- CppCoreGuidelines VS git-internals-pdf
- CppCoreGuidelines VS github-cheat-sheet
- CppCoreGuidelines VS Power-Fx
- CppCoreGuidelines VS too-many-lists
- CppCoreGuidelines VS LearnOpenGL
- CppCoreGuidelines VS dmd
- CppCoreGuidelines VS learnxinyminutes-docs
- CppCoreGuidelines VS clojure-style-guide
- CppCoreGuidelines VS adventofcode