Jacob Lifshay

@joshtriplett before you close this, don't we need a tracking issue?

this seems closely related to `mut(self)` fields https://github.com/rust-lang/rfcs/pull/3323 which should probably be mentioned.

> I'm not sure what happens if you have a macro in the same scope as a function and/or variable of the same name but you may wish to check...

> I maintain that getting input _without_ a prompt is nonsensical. It's a use case that doesn't exist. that's not true, many programs don't prompt before trying to read input,...

> TBH what I really want for this is a `const Trait`-based approach that's extensible for everyone. I think that would need the source text including the sign to be...

> The "only literals, not expressions" logic has some interaction with [rust-lang/compiler-team#835](https://github.com/rust-lang/compiler-team/issues/835) in that if literals do not have signs, this coercion would be limited to positive values only, which...

> Versus: > > ``` > const INTERMEDIATE: u32 = 123 + 456; > const WEIRD: MyWeirdInt = INTERMEDIATE; > ``` > > Now to be clear I recognize that...

> Is your intention that the following would be legal? > > ```rust > let x = 5; > let y: NonZeroU8 = x; > ``` I'd expect that to...

> > 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...

> ``` > let x = 62 as char; > ``` tbh i'm surprised that compiles...