Coding Style for Futhark C Runtime Component == * Use two spaces for indentation, no tabs. * Try to stay below 80 characters per line. * Braces are mandatory for control flow structures. * Use only line comments. * Use snake_case for naming, except preprocessor macros, which are uppercase. * Check all return values. * Do not use header guards, and do not include one RTS header from another. The header files here are not intended to be used as normal C header files, but are instead copied into the generated program in a specific order. An argument could be made that perhaps they ought be `.c` files instead. * Start all files with the comment `// Start of foo.h.` and end with `// End of foo.h.`. This makes the concatenated code easier to navigate. * Ensure, as far as possible, that the code is also valid C++.