Figure out how to preserve reading material and references

[felix91gr]

There's a decent chunk of material that's been useful for working on the Guidelines. It probably merits its own section in the main guidelines document.

For now though, while we figure out how and where to store them, let this issue serve as a central place to collect them.

[felix91gr]

Pointer Provenance

Note: this was originally written in Aug 6, 2025

Important Links

1. Gankra (Aria Desires) wrote extensively about the issues that pointer types have in Rust, and proposed ways in which to tackle these issues, in 2022.
2. In January 2025, those APIs were stabilized.
3. Here's the documentation on how to use said Strict Provenance APIs.
   (Fun fact: these APIs not only help with correctness; they also enable better compiler optimizations 🔥)
4. As tends to be the case with Rust, there's an API for use cases where provenance cannot be obtained. Like for bare metal applications, where as I currently understand it, it's not that uncommon to have to conjure up a pointer from thin air (to eg use memory-mapped hardware): exposed provenance.

Discussion Jumping Points

1. Here is where we start discussing the CERT C: INT36-C rule, "Converting a pointer to integer or integer to pointer".
2. And here's my summary of the current consensus we've reached.

[felix91gr]

Clippy Lints

#86 contains all the details of the research we've done together with @sei-dsvoboda regarding Clippy Lints and their applicability to our work.