otomatalabs/furnace
7
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

update contributing guidelines

Browse source
This commit is contained in:
tildearrow 2023-12-09 15:31:24 -05:00
parent 48622337f7
commit 0daf52ffe0
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
CONTRIBUTING.md
View file

@ -35,6 +35,7 @@ the coding style is described here:
- preprocessor directives not intended - preprocessor directives not intended
- if macro comprises more than one line, indent - if macro comprises more than one line, indent
- no new line after `template<>` - no new line after `template<>`
- do not use `_t` types, except for 64-bit integers and `size_t`.
- prefer built-in types: - prefer built-in types:
- `bool` - `bool`
- `signed char` or `unsigned char` are 8-bit - `signed char` or `unsigned char` are 8-bit
@ -48,6 +49,7 @@ the coding style is described here:
- `long long int` or `unsigned long long int` are 64-bit - `long long int` or `unsigned long long int` are 64-bit
- avoid using 64-bit numbers as I still build for 32-bit systems. - avoid using 64-bit numbers as I still build for 32-bit systems.
- two `long`s are required to make Windows happy. - two `long`s are required to make Windows happy.
- prefer using `int64_t` or `uint64_t` for this specific case.
- `size_t` are 32-bit or 64-bit, depending on architecture. - `size_t` are 32-bit or 64-bit, depending on architecture.
- 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`.