@Rogue@snaggen Yeah, it’s a setting in Cargo.toml that you have to update manually if you want to upgrade. It is set to latest edition in new projects. And the nice thing:
it’s configurable per-crate, not per-compilation. So you can depend on crates that use different editions than your crate. Which avoids ecosystem fragmentation.
it’s configurable per-crate, not per-compilation. So you can depend on crates that use different editions than your crate. Which avoids ecosystem fragmentation.
Thanks! That pre-empted my next question of how quickly crates typically update to newer editions. I guess it doesn’t matter
There is also cargo fix --edition which can update your code in a very conservative way automatically. The result might not be as idiomatic but errs on the side of having semantics that do not change.
@Rogue @snaggen Yeah, it’s a setting in Cargo.toml that you have to update manually if you want to upgrade. It is set to latest edition in new projects. And the nice thing:
it’s configurable per-crate, not per-compilation. So you can depend on crates that use different editions than your crate. Which avoids ecosystem fragmentation.
Thanks! That pre-empted my next question of how quickly crates typically update to newer editions. I guess it doesn’t matter
There is also
cargo fix --editionwhich can update your code in a very conservative way automatically. The result might not be as idiomatic but errs on the side of having semantics that do not change.