-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Release notes for 1.76 #120004
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Release notes for 1.76 #120004
Conversation
@Mark-Simulacrum: no appropriate reviewer found, use r? to override |
r? @cuviper |
82abe89
to
8f1573a
Compare
@bors r+ rollup p=1 |
🌲 The tree is currently closed for pull requests below priority 100. This pull request will be tested once the tree is reopened. |
…iaskrgr Rollup of 10 pull requests Successful merges: - rust-lang#119543 (add avx512fp16 to x86 target features) - rust-lang#120004 (Release notes for 1.76) - rust-lang#120562 (Revert unsound libcore changes) - rust-lang#120566 (coverage: Use normal `edition:` headers in coverage tests) - rust-lang#120570 (Suggest changing type to const parameters if we encounter a type in the trait bound position) - rust-lang#120571 (Miscellaneous diagnostics cleanups) - rust-lang#120573 (Remove `BorrowckErrors::tainted_by_errors`) - rust-lang#120592 (Remove unnecessary `.to_string()`/`.as_str()`s) - rust-lang#120610 (hir: Remove the generic type parameter from `MaybeOwned`) - rust-lang#120616 (Fix ICE on field access on a tainted type after const-eval failure) Failed merges: - rust-lang#120569 (coverage: Improve handling of function/closure spans) r? `@ghost` `@rustbot` modify labels: rollup
…iaskrgr Rollup of 10 pull requests Successful merges: - rust-lang#119543 (add avx512fp16 to x86 target features) - rust-lang#120004 (Release notes for 1.76) - rust-lang#120562 (Revert unsound libcore changes) - rust-lang#120566 (coverage: Use normal `edition:` headers in coverage tests) - rust-lang#120570 (Suggest changing type to const parameters if we encounter a type in the trait bound position) - rust-lang#120571 (Miscellaneous diagnostics cleanups) - rust-lang#120573 (Remove `BorrowckErrors::tainted_by_errors`) - rust-lang#120592 (Remove unnecessary `.to_string()`/`.as_str()`s) - rust-lang#120610 (hir: Remove the generic type parameter from `MaybeOwned`) - rust-lang#120616 (Fix ICE on field access on a tainted type after const-eval failure) Failed merges: - rust-lang#120569 (coverage: Improve handling of function/closure spans) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#120004 - Mark-Simulacrum:relnotes-1.76, r=Mark-Simulacrum Release notes for 1.76 Cargo, library stabilizations and some cleanups, particularly to future compat, still pending. cc `@cuviper` `@rust-lang/release`
Not sure where to best ask this - I was wondering if this should explicitly point out that win7 support is being dropped from the tier 1 windows target, in addition to the new separate win7 target? |
Did a PR dropping that support actually land? The platform support file and quick skim of history doesn't show that we have declared the drop of support. So I think the earliest it will likely happen now is 1.78 (current nightly). |
Per rust-lang/compiler-team#651, the decision is to drop the support in 1.76, and we announced it in the 1.72 release post (although #115141 has not be merged yet.) |
We've already built artifacts etc, so I think it'll slip to 1.77 at least, this doesn't seem like something worth rebuilding artifacts for. |
Yes, sorry, it's fine to let it slip to 1.77. The intent was to have a blog post out earlier explaining things (and the new win7 target) but I've had a busy new year and not been on top of things. In retrospect it was silly to schedule it so early in the year. |
Cargo, library stabilizations and some cleanups, particularly to future compat, still pending.
cc @cuviper @rust-lang/release