Contributions to this project must be accompanied by a Contributor License Agreement. You (or your employer) retain the copyright to your contribution; this simply gives us permission to use and redistribute your contributions as part of the project.
- Please see repo layout.
In general, please use clang-format to format code, and follow clang-tidy tips.
Most of the code style is derived from the Google C++ style guidelines, except:
- Exceptions are allowed and encouraged where appropriate.
- Header guards should use
#pragma once
. - Adopts camelBack for function names.
The compiler portion of the project follows MLIR style.
- Git commit message should be meaningful, we suggest imperative keywords.
- Developer must write unit-test (line coverage must be greater than 80%), tests should be deterministic.
- Read awesome Abseil Tips
SPU recommends users "live-at-head" like abseil-cpp, just like abseil, spu also provide Long Term Support Releases to which we backport fixes for severe bugs.
We use the release date as the version number, see change log for example.
Please keep updating changes to the staging area of change log Changelog should contain:
- all public API changes, including new features, breaking changes and deprecations.
- notable internal changes, like performance improvement.