3 ms·
I think your parent is exaggerating a bit, but this is just generally true of any release with a bug feature in it that people are excited to use. Now that it e
by steveklabnik 8y ago
I think your parent is exaggerating a bit, but this is just generally true of any release with a bug feature in it that people are excited to use. Now that it exists, why would you not want to use it?
For context, Rust 1.31 is sorta like the Go 2 release. It’s a much bigger deal than regular releases.
- ploxiln 8y agoIf you're writing a toy/exercise, sure, have fun, I support that. It's part of developing your skills and thinking about software. If you're writing infrastructure, please don't. (e.g. Firefox ... or the toolchain itself) I'm one of those guys with no particular interest in Go 2. I really have plenty to work with already.
- gilnaa 8y agoIt's not always up to me which compiler version I use. Some organizations change compilers very slowly, and you can't assume you always have the most updated compiler. For example, when writing a library for my org I assumed that GCC 5.4 (2016) is a reasonable lower bound, and I used the appropriate set of supported C++11 features, and twice I had to downgrade as different teams notified me they had older and older compilers. (and couldn't upgrade)
- deleted 8y ago[deleted]