Meeting 2025-03-19

Critical

Status Reports

Discussion Questions

SANITY Comments

Danilo suggested to have SANITY comments similar to SAFETY comments: https://lore.kernel.org/all/Z9hGcClQXpEYUYZp@cassiopeiae/

A couple points from me:

  • we shouldn't use SANITY, on a quick glance it seems similar to SAFETY and we should be very vary of confusion between the two
  • I'm not sure if they have a consistent format or phrasing, safety comments do. But for sanity stuff I'm not sure what one would write in general.

Boqun: how about FORGET: ;-)

Benno: how about FOOTGUN

Miguel: how about PITFALL

Danilo: JUSTIFY?

Benno: I wouldn't use JUSTIFY, since that sounds a lot like the language that I use for safety comments.

Tamir: CAUTION

Danilo: Maybe people will abuse this by using this feature as opposed to designing a good API.

/// # Pitfalls
///
/// ...
fn forget<T>(t: T);


// PITFALL: ...
forget(..);

Miguel: notes about previous discussions on colored unsafe (unsafe(...)), as well as // CAST etc.

Boqun: could forget be unsafe?

strict_provenance API

See https://lore.kernel.org/all/20250317-ptr-as-ptr-v5-6-5b5f21fa230a@gmail.com/ and my discussion with Alice: https://lore.kernel.org/all/Z9lnIJCcVSza6UVo@google.com/

We should also globally allow https://rust-lang.github.io/rust-clippy/master/index.html#incompatible_msrv.

generate_rust_analyzer.py needs type hints review

Plz.

https://lore.kernel.org/all/20250311-rust-analyzer-host-v2-4-30220e116511@gmail.com/

Miscellaneous