[nostalgia] Remove anti-references policy from dev handbook
This commit is contained in:
		| @@ -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 | ||||
| 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 | ||||
|  | ||||
| ### Error Handling | ||||
|   | ||||
		Reference in New Issue
	
	Block a user