-
Notifications
You must be signed in to change notification settings - Fork 13.9k
[beta-1.91] Add more context to the temporary lifetime extension FCW #148174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Conversation
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
…mulacrum [beta] Initial cut for 1.91 beta https://forge.rust-lang.org/release/process.html#beta-pr Also backports: - Only run Cranelift dist test on nightly rust-lang#146582 r? `@Mark-Simulacrum`
This reverts commit 095fa86.
…youxu [beta] Revert "compiler: Add Windows resources to rustc-main and rustc_driver" This reverts rust-lang#146018 due to rust-lang#146693
…mulacrum [beta] bump to released stable compiler https://forge.rust-lang.org/release/process.html#beta-stage0-update-friday r? `@Mark-Simulacrum`
…iser Revert "Auto merge of rust-lang#144086 - clubby789:alloc-zeroed, r=nikic" This reverts commit 040a98a, reversing changes made to e8a792d. This reverts rust-lang#144086 on beta due to rust-lang#145995. On master the issue will be fixed by rust-lang#146766.
(cherry picked from commit 4fcafc9)
(cherry picked from commit 83532f8)
(cherry picked from commit 5a4e536)
(cherry picked from commit 5c95f8b)
(cherry picked from commit 1c85a1d)
[beta] backports - remove incorrect fast path rust-lang#146919 - Fix infinite recursion in Path::eq with String rust-lang#146958 - Make #[link="dl"] an FCW rather than an error rust-lang#147262 r? cuviper
(cherry picked from commit e3f1046)
Signed-off-by: Jonathan Brouwer <jonathantbrouwer@gmail.com> (cherry picked from commit 4787834)
(cherry picked from commit 1589c6c)
When building with `rust.rpath = false`, every `rustc` invocation needs to include the library path as well. I particularly ran into this in `generate_target_spec_json_schema` when testing 1.91-beta in Fedora, where we do disable rpath for our system builds. The new helper function will hopefully encourage the right thing going forward. (cherry picked from commit 03cdcb5)
(cherry picked from commit 95ddfa1)
(cherry picked from commit a3482d9)
[beta] backports - Don't normalize higher-ranked assumptions if they're not used rust-lang#147299 - Fix target list of `link_section` rust-lang#147418 - bootstrap: add `Builder::rustc_cmd` that includes the lib path rust-lang#147419 - Update LLVM to 21.1.2 rust-lang#146953 - Remove the temporary directory when a check ends -- part of rust-lang#147518 r? cuviper
…nglo [beta-1.91] Update cargo submodule 2 commits in 785a383cf715417fcd68c4a98a4523c2d082bb0f..ea2d97820c16195b0ca3fadb4319fe512c199a43 2025-10-04 19:17:20 -0500 to 2025-10-10 15:19:24 -0400 - [beta-1.91] fix: use `host-tuple` for host target subsitution (rust-lang/cargo#16032) - [beta-1.91] fix(timings): compute codegen start time to draw dep lines (rust-lang/cargo#16057) r? ghost
(cherry picked from commit ebd5bea)
(cherry picked from commit 4a4f3b0)
(cherry picked from commit dd83c57)
(cherry picked from commit a81ed52)
…th multi byte chars The issue cannot be reproduced with the former testcase of creating external crates because rust refuses to use "external crate 28_找出字符串中第一个匹配项的下标" because it is not a valid indentifier (starts with number, and contain non ascii chars) But still using 28_找出字符串中第一个匹配项的下标.rs as a filename is accepted by previous rustc releases So we consider it valid, and add an integration test for it to catch any regression on other code related to non ascii filenames. (cherry picked from commit c6acffe)
[beta] backports - Revert constification of `AsRef for Cow` due to inference failure rust-lang#148011 - Revert constification of `Borrow` and `Deref for Cow` due to inference failure rust-lang#148016 - Revert "fix: Filter suggestion parts that match existing code" rust-lang#148043 - Revert "feat: implement `hash_map!` macro" rust-lang#148049 - fix panic when rustc tries to reduce intermediate filenames len with utf8 rust-lang#148018 r? cuviper
fmease
reviewed
Oct 27, 2025
Mention in the FCW that the lifetime extension behavior was wrong since 1.88/1.89.
94e8a42 to
6ab240d
Compare
BoxyUwU
approved these changes
Oct 27, 2025
f2f881b to
f435972
Compare
|
☔ The latest upstream changes (presumably #142712) made this pull request unmergeable. Please resolve the merge conflicts. |
|
I just moved the branches, but I can pull this into the stable PR. |
|
Channel promotion happened. Contained in / superseded by #148179. Closing. |
bors
added a commit
that referenced
this pull request
Oct 27, 2025
[stable] Prepare Rust 1.91.0 release - [beta-1.91] Add more context to the temporary lifetime extension FCW #148174 - rustdoc-search: JavaScript optimization based on Firefox Profiler output #146484 - rustdoc-search: use the same ID for entry and path to same item #147045 - rustdoc-search: stringdex update with more packing #147002 - rustdoc-search: stringdex 0.0.2 #147660 - [beta] Clippy beta backport #148029 - 1.91.0 release notes #148013 r? cuviper
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
beta-accepted
Accepted for backporting to the compiler in the beta channel.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
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.
Mention in the FCW that the lifetime extension behavior was wrong since 1.88/1.89.
This was suggested by @cyqsimon in #145838 (comment), with the aim of helping users understand the potential scope of the breakage.
I apologize if this PR is too late in the release process. Feel free to close it if it is.
cc @dianne @cuviper