Top CppCoreGuidelines issues

C.128: Should destructors be marked "override"?

jaredgrubb·5 Sep 2016·16 Comments

SF.1: Default convention for C++ header files should be .hpp (matching .cpp)

declined

GiovanniDicanio·19 Aug 2016·24 Comments

👍12

std::string_view encourages use-after-free; the Core Guidelines Checker doesn't complain

kcc·26 Sep 2017·31 Comments

👍14

Proposal to outlaw std::endl

resolved

Florianjw·24 Oct 2015·44 Comments

F5 is horribly wrong. You should ALWAYS declare your function as inline if it does not mean extern.

lytvqa·1 Jun 2020·22 Comments

👎2 😄1

Give a split view of the Guidelines when vied on a phone by chapters.

AraHaan·8 May 2017·22 Comments

❤4 👍3

C.128, why not use override virutal base class destructor?

franzhollerer·23 Jul 2017·5 Comments

👍6

C.131: Please reconsider this rule; trivial getters and setters can make sense

GiovanniDicanio·17 Oct 2016·21 Comments

👍4

Avoid iostream and cstdio

declined

expnkx·9 Mar 2020·16 Comments

Renaming CP.25 raii_thread, and fixing CP.26 detached_thread

resolved

hsutter·9 May 2017·46 Comments

👍5

Next issues