update contributing guidelines

This commit is contained in:
tildearrow 2024-03-17 17:52:52 -05:00
parent 43ddfb8b5e
commit 2dd5e85299

View file

@ -54,7 +54,8 @@ the coding style is described here:
- in float/double operations, always use decimal and `f` if single-precision. - in float/double operations, always use decimal and `f` if single-precision.
- e.g. `1.0f` or `1.0` instead of `1`. - e.g. `1.0f` or `1.0` instead of `1`.
- prefer `NULL` over `nullptr` or any other proprietary null. - prefer `NULL` over `nullptr` or any other proprietary null.
- don't use `auto` unless needed. - only use `auto` if needed.
- avoid using `goto` unless absolutely required.
- use `String` for `std::string` (this is typedef'd in ta-utils.h). - use `String` for `std::string` (this is typedef'd in ta-utils.h).
- prefer using operator for String (std::string) comparisons (a==""). - prefer using operator for String (std::string) comparisons (a=="").
- if you have to work with C strings, only use safe C string operations: - if you have to work with C strings, only use safe C string operations: