Coding Style

The coding style for rav1e code follows the Rust Style Guide, with the following exceptions:

• Each indentation level is 2 spaces.

Assertions

Assertions should never be reachable by any sequence of API calls.

Assertions should never be reachable by any sequence of crav1e API calls which do not depend on C undefined behavior, or contain pointers that cause invalid behavior when accessed.

Prefer assert()! to debug_assert()! in the following situations: - Unsafe code. - Code called once per tile or less where debug build testing is unlikely to expose errors (for example, the tests are #[ignored] by default, or it is not covered by unit tests at all)