You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The game usually doesn't work with raw types in functions, but mostly references or pointers to objects (except Vector/Matrix, which can occur very often, but auto can be avoided here by using implicit constructors instead). While auto is not technically wrong and often still matches, it is still obscuring the unterlying type. Sometimes, this might be fine (for example new calls), but for these circumstances, we should still have the * or & directly annotated on the type, to avoid confusion.
The text was updated successfully, but these errors were encountered:
The game usually doesn't work with raw types in functions, but mostly references or pointers to objects (except
Vector/Matrix
, which can occur very often, butauto
can be avoided here by using implicit constructors instead). Whileauto
is not technically wrong and often still matches, it is still obscuring the unterlying type. Sometimes, this might be fine (for examplenew
calls), but for these circumstances, we should still have the*
or&
directly annotated on the type, to avoid confusion.The text was updated successfully, but these errors were encountered: