News for hackers. Stuff that matters.
Re:RFC: Evolving Rust Through Epochs by cpeterso on Tuesday July 04, 2017 @07:35PM (#14698987)
If the Rust compiler promises to support all previous epochs, can it ever remove the compiler code that implements deprecated language features?
Re:RFC: Evolving Rust Through Epochs by JoshTriplett on Tuesday July 04, 2017 @08:06PM (#14699120)
No, and they've specifically specified it as always available. Just as GCC still supports C89.

However, they also specified this as only affecting translation/desugaring, which makes the additional code minimally invasive.

Re:RFC: Evolving Rust Through Epochs by Manishearth on Tuesday July 04, 2017 @09:13PM (#14699377)
Epochs are primarily deprecated syntax behavior, so it's more like branches in the parser or other relatively self-contained bits. As the RFC says, the core language will continue to stay the same.

So I don't see this as leading to some major accumulation of cruft.

Re:RFC: Evolving Rust Through Epochs by tyoverby on Tuesday July 04, 2017 @08:04PM (#14699111)
I work on the C# compiler and the answer over in that world is "no"; everything needs to be supported.
Re:RFC: Evolving Rust Through Epochs by bpicolo on Tuesday July 04, 2017 @07:56PM (#14699080)
Perhaps it could move them to packages as compiler plugins? That could be more or less tricky depending on the piece though.