drinkingtea/nostalgia
drinkingtea/nostalgia
2
0
Fork 0
Code Issues 6 Pull Requests Actions Releases 6 Activity

[nostalgia] Remove anti-references policy from dev handbook

Browse Source
This commit is contained in:
Gary Talent 2023-05-30 20:55:20 -05:00
parent d598efb5ea
commit 437b33cdb5
1 changed files with 0 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
developer-handbook.md
View File

@ -128,18 +128,6 @@ the entire life of the process, other classes likely will not get away with it
due to more substantial constructors and more frequent instantiations of the due to more substantial constructors and more frequent instantiations of the
classes in question. classes in question.
### Pointers vs References
Pointers are generally preferred to references. References should be used for
optimizing the passing in of parameters and for returning from accessor
operators (e.g. ```T &Vector::operator[](size_t)```).
As parameters, references should always be const.
A non-const reference is generally used because the parameter value is changed
in the function, but it will look like it was passed in by value where it is
called and thus not subject to change.
The reference operator makes it clear to the caller that the value can and
likely will change.
## Project Systems ## Project Systems
### Error Handling ### Error Handling