On Tue, Dec 8, 2020 at 10:51 PM David A. Wheeler <[email protected]> wrote:
> For example, the current code uses the deprecated “try!” macro. Current > Rust compiler & documentation urge use of the easier “?” construct, and I > expect “try!” to stop being supported (“try” is becoming a keyword with > different semantics). Using a construct that is going to be eliminated is > *very* user-visible, especially once it stops compiling :-). I want the > code to compile on recent versions of Rust compilers; newer compilers tend > to produce faster code. > Just for reference, the way rust works, it won't ever stop compiling, but it is instead tied to an "edition", probably the 2015 edition for this code, and upgrading the edition is the only time deprecated features can be turned into errors or repurposed. The reason for this design is exactly so that you don't have this bargain to make: you can keep upgrading the compiler, get faster code, but signal that you want 2015 semantics by setting the edition, and try! will keep working as is. Mario -- You received this message because you are subscribed to the Google Groups "Metamath" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/metamath/CAFXXJStqc5MfBL7OM-DJc_xEPgPtM7%3DAqU%2BgV4WeUra2RRs3jg%40mail.gmail.com.
