Closed
Conversation
Member
|
Do conda-forge and Homebrew support this yet? |
Member
Author
|
homebrew is at 1.85 (https://formulae.brew.sh/formula/rust), conda-forge is still on 1.84 (https://anaconda.org/conda-forge/rust). |
Collaborator
|
Seems like conda-forge is now at 1.85 |
Member
|
We're planning to setup an official MSRV policy. The current plan is to use N-2 (so, we always use 2-versions earlier than the latest stable) as our MSRV. I need to update our versioning documentation to reflect it though. |
Member
|
See: #11898 |
Member
Author
|
Closing this (too many merge conflicts) in favor of recreating it when 1.87 ships and 1.85 with the initial edition 2025 support is N-2. |
konstin
added a commit
that referenced
this pull request
Mar 3, 2025
Three edition 2021 compatible sets of changes in preparation for the edition 2025 split out from #11724. In edition 2025, `gen` is a keyword, so we escape it as `r#gen`. `ref` and `ref mut` are not allowed anymore for `&T` and `&mut T`, so we remove them. `cargo fmt` now formats inside of macros, which the 2021 formatter doesn't undo.
konstin
added a commit
that referenced
this pull request
Mar 3, 2025
Three edition 2021 compatible sets of changes in preparation for the edition 2025 split out from #11724. In edition 2025, `gen` is a keyword, so we escape it as `r#gen`. `ref` and `ref mut` are not allowed anymore for `&T` and `&mut T`, so we remove them. `cargo fmt` now formats inside of macros, which the 2021 formatter doesn't undo.
Closed
charliermarsh
added a commit
that referenced
this pull request
May 18, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update to Rust 2025, replace one
|...| asyncwithasync |...|(other interesting closures are tracing-instrumented) and all|...| async movewithasync |...|.The changes are generally
cargo fix,cargo fmtand occasional manual editing wherecargo fixfailed, such as removing theref muts andrefs for values that are already references, which is forbidden in the 2025 edition.