Upgrade to Rust 1.90 #124
Labels
No labels
bug
design
duplicate
engine
enhancement
maintenance
prospective
question
regression
stub
todo
ui
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: StudioInfinity/dyna3#124
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This is the current stable version. The Rust team plans to stabilize 1.91 on Oct. 30, 2025.
Is there a motivation for continuously tracking stable Rust? Or should we just wait for Oct 30? Is there a way to automate Rust-bump PRs and if so, would we want to do that?
The cost of being a few releases behind shouldn't be too high, but we do benefit from new Rust features. For example, pull request #84 bumped the Rust version from 1.85 to 1.86 so we could use a newly stabilized trait object upcasting feature. We also have a very minor simplification waiting on the future stabilization of an experimental feature.
Because I like to keep pull requests focused, doing periodic dedicated Rust upgrade PRs seems like less work to me than combining a new feature and a Rust upgrade in the same PR.