-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce a section on best practices #78
Comments
Some more ideas:
And on the repetition side:
|
Definitely. I feel like for new comers this should give some pointers on doing things in mostly correct way
👍
Yeah this would be nice, esp. understanding ownership, ie. naked pointers as a view only resource |
As we discussed just now in our meeting, here are the ATLAS coding standards. Which could be pointed to, together with those of the other experiments. 😉 http://atlas-computing.web.cern.ch/atlas-computing/projects/qa/draft_guidelines-0.2.html |
Decided to make a box/design for making good practices easily recognisable, and put the good practices right next to the places where the rationales can be explained. |
I think we should discuss the SOLID principles at the end of the OOP chapter to give some guidance: https://en.wikipedia.org/wiki/SOLID |
Closing in favour of #507 |
Since this is a fairly generic idea, for starts we could introduce a simple slide linking to Core Guidelines (https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines). Maybe we could cherry-pick a few guidelines that are commonly considered good, for eg:
(Fairly opinionated list ;)
The text was updated successfully, but these errors were encountered: