ticki

On a sidenote, this has been proposed multiple times, but often rejected due to introducing typestate. I'd just like to note, that it can be done without typestates, solely with...

@bjz, mod types are a lot simpler.

Also, I would prefer having a function like `shrink` instead of `as?`.

More ideas in a similar style can be found here: 1. https://github.com/rust-lang/rfcs/issues/671 2. https://github.com/rust-lang/rfcs/pull/45 3. https://github.com/bill-myers/rfcs/blob/no-integer-overflow/active/0000-no-integer-overflow.md 4. https://www.reddit.com/r/rust/comments/43xbg2/why_this_error_was_not_detected_on_compile_time/

@Exagone313 I didn't suggest machine learning.

@Kimik0 I think it should be an option, not default necessarily

Big :+1:. It would be very nice to have such feature.

A basic matrix, which should cover the majority of cases: ``` COMPATIBLE WITH > PD MIT BSD AL LGPL LGPL+ LGPL3 MPL GPL GPL+ GPL3 AGPL Public Domain ✔ ✔...

@burdges @Nemo157 @tbu- It is based on the fact that these licenses are transitive with each other. If you extend the set, it might not be transitive, though.

> How would such an option affect the f32 and f64 types in the language? Would any use of these types become an a compile-time error? Nope. They'll just not...