I am starting a new project in C++11, and just found out about the delete
keyword that lets you prevent accidental calling of copy constructors and so on. Is there a "recommended" set of deletions I can do globally to increase type safety, such as preventing signed to unsigned cast within expressions? Should I default to delete
ing all 5 operations that I can delete
in all my classes?
FYI, this program requires high performance (thats why I'm using C++, for the first time in years) and there are very few times I want to copy anything, so a copy is usually a bug, although not 100% of the time, so I'm interested in this specific case, as well as the general case for other programs. I could potentially delete
the copy constructor and add a separate method that copies the object for the rare time that I do need a copy. Would that be a good idea?
Aucun commentaire:
Enregistrer un commentaire