Oli Scherer

I think should fix the read functions before making the write functions do anything

We need to update the RFC first to reflect the latest effect design (assoc types instead of const generic bool params ) Edit: oh I thought this was the effects...

Is your intention that the following would be legal? ```rust let x = 5; let y: NonZeroU8 = x; ``` Because that's an order of magnitude more impl work than...

Cool. Yea maybe add it to the future possibilities section. And add an example to the reference section stating that it's explicitly not supported

> wouldn't the type deduction semantics be similar to: We'd need to either go the route where we allow this for all types that implement specific traits or add more...

Just want to make sure what is being proposed. Because what @programmerjake is asking for needs a lot more reference level explanations and some guide level explanations

> since this works: > > ```rust > let a = 45; > let b: u8 = a; > ``` That works because integer literals not matching their type's range...

`let a = 45;` gives `a` and the `45` an inference type, not type `u8`. After the fact, the `let b: u8 = a;` turns that inference type into a...

cool, this seems really useful!

> * I think that should be possible? Or does the rustc driver infrastructure assume that it is instantiated only once per process? Possible, we only use tls, no true...