cpp-best-practices / cpp-best-practices/cppbestpractices

Clarify that marking certain member variables const can hinder performance

Aperta
#147 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Nessun dato sulla lingua
Stelle
8.8k
Fork
902
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

In the 03-Style document, I read the following sentence:

> If the member variable is not expected to change after the initialization, then mark it const.

However, we know that if, for example, we mark a container as `const`, we prevent it from being moved, possibly hindering performance. Marking fields as `const` is useful to enforce invariants; however, it "interferes" with performance. If both const correctness and performance are important, one could leave the field non-const, make it private and define a field getter.

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.