a-mir-formality
a-mir-formality copied to clipboard
rust-lang
a model of MIR and the Rust type/trait system
The ty layer has a notion of "schemes" which are the result of proving something is true; they basically pair up a bunch of inference variables with relationships between those...
We need to support auto traits: * [ ] Extract trait declarations with an (optional) `auto` qualifier; perhaps in the form of a "flag list" that leaves room for other...
I think we will base this design on polonius. There are various pieces to the borrow checker: * [x] #84 * [ ] Region check -- detect errors from HRTB,...
We need to add a "type-check" for functions with the following parts: ### Decl layer * Assuming: * function where-clauses hold * argument and return types are "valid" (need a...
Depends on #25 Convert ```rust static UNIT: &'static &'static () = &&(); fn foo(_: &'a &'b (), v: &'b T) -> &'a T { v } fn bad &'static T...
We need a way to add MIR declarations to things like statics, consts, etc. I imagined this as a separate "map" that took the item name and connected it to...
Instead of having a scalar type be `(rigid-ty i32 ())` we should make it `(rigid-ty i32-scalar ())` or something like that, and then alias that term to `i32`. This way...
According to https://doc.rust-lang.org/reference/special-types-and-traits.html#copy one also has to check that `Drop` is not implemented for a type that implements `Copy`. As far as I can tell this can't be stated currently...
but we're not really testing it in any useful way. cc @voidc