Skip to content

WF check lifetime bounds for locals with type params#149389

Merged
rust-bors[bot] merged 2 commits intorust-lang:mainfrom
ShoyuVanilla:local-region-param-wf
Feb 14, 2026
Merged

WF check lifetime bounds for locals with type params#149389
rust-bors[bot] merged 2 commits intorust-lang:mainfrom
ShoyuVanilla:local-region-param-wf

Conversation

@ShoyuVanilla
Copy link
Copy Markdown
Member

@ShoyuVanilla ShoyuVanilla commented Nov 27, 2025 •
edited by lcnr
Loading

FCP proposal in #149389 (comment)

Fixes #115175
Fixes #148854

@rustbot rustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Nov 27, 2025
@ShoyuVanilla
Copy link
Copy Markdown
Member Author

ShoyuVanilla commented Nov 27, 2025

@bors try

@rust-bors

This comment has been minimized.

Sign in to view
rust-bors bot added a commit that referenced this pull request Nov 27, 2025
@rust-bors
Auto merge of #149389 - ShoyuVanilla:local-region-param-wf, r=<try>
5ce1ef4 
WF check lifetime bounds for locals with type params
@rust-log-analyzer

This comment has been minimized.

Sign in to view
@rust-bors
Copy link
Copy Markdown
Contributor

rust-bors bot commented Nov 27, 2025

☀️ Try build successful (CI)
Build commit: 5ce1ef4 (5ce1ef4ffbf1e6d8c09f46fa655ea765bacf4427, parent: cf8a95590a1b768b7711f2631d5b5e3ead464de7)

@ShoyuVanilla
Copy link
Copy Markdown
Member Author

ShoyuVanilla commented Nov 27, 2025

@bors try

rust-bors bot added a commit that referenced this pull request Nov 27, 2025
@rust-bors
Auto merge of #149389 - ShoyuVanilla:local-region-param-wf, r=<try>
f70ee28 
WF check lifetime bounds for locals with type params
@rust-bors

This comment has been minimized.

Sign in to view
@rust-bors
Copy link
Copy Markdown
Contributor

rust-bors bot commented Nov 27, 2025

☀️ Try build successful (CI)
Build commit: f70ee28 (f70ee28831acc074c109afab32d287057c3eca46, parent: cf8a95590a1b768b7711f2631d5b5e3ead464de7)

@ShoyuVanilla
Copy link
Copy Markdown
Member Author

ShoyuVanilla commented Nov 28, 2025

@craterbot check

@craterbot
Copy link
Copy Markdown
Collaborator

craterbot commented Nov 28, 2025

👌 Experiment pr-149389 created and queued.
🤖 Automatically detected try build f70ee28
🔍 You can check out the queue and this experiment's details.

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

@craterbot craterbot added S-waiting-on-crater Status: Waiting on a crater run to be completed. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Nov 28, 2025
@craterbot
Copy link
Copy Markdown
Collaborator

craterbot commented Dec 6, 2025

🚧 Experiment pr-149389 is now running

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

@craterbot
Copy link
Copy Markdown
Collaborator

craterbot commented Dec 7, 2025

🎉 Experiment pr-149389 is completed!
📊 5 regressed and 3 fixed (746168 total)
📊 2051 spurious results on the retry-regessed-list.txt, consider a retry1 if this is a significant amount.
📰 Open the summary report.

⚠️ If you notice any spurious failure please add them to the denylist!
ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

Footnotes

  1. re-run the experiment with crates=https://crater-reports.s3.amazonaws.com/pr-149389/retry-regressed-list.txt ↩

@craterbot craterbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-crater Status: Waiting on a crater run to be completed. labels Dec 7, 2025
@ShoyuVanilla
Copy link
Copy Markdown
Member Author

ShoyuVanilla commented Dec 8, 2025

@craterbot check crates=https://crater-reports.s3.amazonaws.com/pr-149389/retry-regressed-list.txt

@craterbot
Copy link
Copy Markdown
Collaborator

craterbot commented Dec 8, 2025

👌 Experiment pr-149389-1 created and queued.
🤖 Automatically detected try build f70ee28
🔍 You can check out the queue and this experiment's details.

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

@craterbot craterbot added S-waiting-on-crater Status: Waiting on a crater run to be completed. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Dec 8, 2025
@petrochenkov
Copy link
Copy Markdown
Contributor

petrochenkov commented Dec 12, 2025

@craterbot p=11
All the small runs will complete in a few hours and won't need to wait for a few days until the long beta runs complete.

@craterbot
Copy link
Copy Markdown
Collaborator

craterbot commented Dec 12, 2025

📝 Configuration of the pr-149389-1 experiment changed.

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

@craterbot
Copy link
Copy Markdown
Collaborator

craterbot commented Dec 13, 2025

🚧 Experiment pr-149389-1 is now running

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

@craterbot
Copy link
Copy Markdown
Collaborator

craterbot commented Dec 13, 2025

🎉 Experiment pr-149389-1 is completed!
📊 0 regressed and 0 fixed (1832 total)
📊 118 spurious results on the retry-regessed-list.txt, consider a retry1 if this is a significant amount.
📰 Open the summary report.

⚠️ If you notice any spurious failure please add them to the denylist!
ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

Footnotes

  1. re-run the experiment with crates=https://crater-reports.s3.amazonaws.com/pr-149389-1/retry-regressed-list.txt ↩

@craterbot craterbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-crater Status: Waiting on a crater run to be completed. labels Dec 13, 2025
@rustbot rustbot added A-CI Area: Our Github Actions CI A-testsuite Area: The testsuite used to check the correctness of rustc T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels Feb 12, 2026
@rustbot
Copy link
Copy Markdown
Collaborator

rustbot commented Feb 12, 2026

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

@ShoyuVanilla
Copy link
Copy Markdown
Member Author

ShoyuVanilla commented Feb 12, 2026

Ok, could you please cherry-pick ojeda@32650a7?

That adds Benno's commit on top of the other one we had.

Thanks!

Huge thanks for really quick fix 😄

@lcnr
Copy link
Copy Markdown
Contributor

lcnr commented Feb 12, 2026

@bors r+

@rust-bors
Copy link
Copy Markdown
Contributor

rust-bors bot commented Feb 12, 2026

📌 Commit 6a3baf6 has been approved by lcnr

It is now in the queue for this repository.

@rust-bors rust-bors bot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Feb 12, 2026
@ojeda
Copy link
Copy Markdown
Contributor

ojeda commented Feb 12, 2026

Huge thanks for really quick fix 😄

You're welcome! This PR shows the value of the kernel CI job as a test case for Rust, given the crater run; so, in a way, I am glad it happened ;)

Credit goes to Benno for the actual patch, and let's see what bors has to say about it... :)

@rust-bors

This comment has been minimized.

Sign in to view
@rust-bors rust-bors bot added merged-by-bors This PR was explicitly merged by bors. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Feb 14, 2026
@rust-bors
Copy link
Copy Markdown
Contributor

rust-bors bot commented Feb 14, 2026

☀️ Test successful - CI
Approved by: lcnr
Duration: 3h 30m 21s
Pushing 29fa07e to main...

@rust-bors rust-bors bot merged commit 29fa07e into rust-lang:main Feb 14, 2026
12 checks passed
@rustbot rustbot added this to the 1.95.0 milestone Feb 14, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Feb 14, 2026

What is this? This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing f403dee (parent) -> 29fa07e (this PR)

Test differences

Show 6 test diffs

Stage 1

  • [ui] tests/ui/regions/wf-bound-region-in-local-issue-115175.rs: [missing] -> pass (J1)
  • [ui] tests/ui/regions/wf-bound-region-in-local-soundness-issue-148854.rs: [missing] -> pass (J1)

Stage 2

  • [ui] tests/ui/regions/wf-bound-region-in-local-issue-115175.rs: [missing] -> pass (J0)
  • [ui] tests/ui/regions/wf-bound-region-in-local-soundness-issue-148854.rs: [missing] -> pass (J0)

Additionally, 2 doctest diffs were found. These are ignored, as they are noisy.

Job group index

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 29fa07e3dbca35d58c0770042f04ba464eb3db4c --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. dist-aarch64-apple: 2h 52m -> 1h 47m (-37.8%)
  2. dist-apple-various: 1h 40m -> 2h 11m (+29.9%)
  3. dist-x86_64-apple: 2h 8m -> 2h 35m (+21.2%)
  4. x86_64-rust-for-linux: 43m 11s -> 50m 23s (+16.7%)
  5. x86_64-gnu-tools: 53m 38s -> 1h 2m (+15.8%)
  6. i686-gnu-nopt-1: 2h 4m -> 2h 21m (+13.9%)
  7. x86_64-gnu-miri: 1h 14m -> 1h 24m (+13.4%)
  8. x86_64-gnu-distcheck: 2h 1m -> 2h 15m (+11.7%)
  9. armhf-gnu: 1h 22m -> 1h 32m (+11.6%)
  10. dist-aarch64-msvc: 1h 36m -> 1h 46m (+10.5%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@rust-bors rust-bors bot mentioned this pull request Feb 14, 2026
Draft
@ShoyuVanilla ShoyuVanilla deleted the local-region-param-wf branch February 14, 2026 06:34
@rust-timer
Copy link
Copy Markdown
Collaborator

rust-timer commented Feb 14, 2026

Finished benchmarking commit (29fa07e): comparison URL.

Overall result: ✅ improvements - no action needed

@rustbot label: -perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

mean range count
Regressions ❌
(primary)		 - - 0
Regressions ❌
(secondary)		 - - 0
Improvements ✅
(primary)		 -0.7% [-0.7%, -0.7%] 1
Improvements ✅
(secondary)		 - - 0
All ❌✅ (primary) -0.7% [-0.7%, -0.7%] 1

Max RSS (memory usage)

Results (primary 1.8%, secondary 2.3%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)		 5.0% [2.9%, 8.8%] 3
Regressions ❌
(secondary)		 5.9% [5.6%, 6.1%] 2
Improvements ✅
(primary)		 -3.0% [-3.7%, -2.3%] 2
Improvements ✅
(secondary)		 -1.3% [-1.6%, -1.0%] 2
All ❌✅ (primary) 1.8% [-3.7%, 8.8%] 5

Cycles

Results (secondary 3.4%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)		 - - 0
Regressions ❌
(secondary)		 3.4% [3.4%, 3.4%] 1
Improvements ✅
(primary)		 - - 0
Improvements ✅
(secondary)		 - - 0
All ❌✅ (primary) - - 0

Binary size

Results (primary 0.0%, secondary 0.0%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)		 0.0% [0.0%, 0.0%] 9
Regressions ❌
(secondary)		 0.0% [0.0%, 0.0%] 1
Improvements ✅
(primary)		 - - 0
Improvements ✅
(secondary)		 - - 0
All ❌✅ (primary) 0.0% [0.0%, 0.0%] 9

Bootstrap: 481.836s -> 480.714s (-0.23%)
Artifact size: 398.12 MiB -> 398.10 MiB (-0.00%)

@rustbot rustbot removed the perf-regression Performance regression. label Feb 14, 2026
github-actions bot pushed a commit to rust-lang/miri that referenced this pull request Feb 15, 2026
@bors
Auto merge of #149389 - ShoyuVanilla:local-region-param-wf, r=lcnr
13963a7 
WF check lifetime bounds for locals with type params

FCP proposal in rust-lang/rust#149389 (comment)

Fixes rust-lang/rust#115175
Fixes rust-lang/rust#148854
@lcnr lcnr mentioned this pull request Feb 17, 2026
Open
Darksonn pushed a commit to Darksonn/linux that referenced this pull request Feb 18, 2026
@BennoLossin @Darksonn
rust: irq: add 'static bounds to irq callbacks
ae9c361 
These callback functions take a generic `T` that is used in the body as
the generic argument in `Registration` and `ThreadedRegistration`. Those
types require `T: 'static`, but due to a compiler bug this requirement
isn't propagated to the function. Thus add the bound. This was caught in
the upstream Rust CI [1].

Signed-off-by: Benno Lossin <lossin@kernel.org>
Link: rust-lang/rust#149389 [1]
Reviewed-by: Gary Guo <gary@garyguo.net>
Fixes: 29e16fc ("rust: irq: add &Device<Bound> argument to irq callbacks")
Link: https://lore.kernel.org/all/20260214092740.3201946-1-lossin@kernel.org/
Reviewed-by: Daniel Almeida <daniel.almeida@collabora.com>
Link: https://lore.kernel.org/r/20260214092740.3201946-1-lossin@kernel.org
Signed-off-by: Alice Ryhl <aliceryhl@google.com>
ojeda pushed a commit to Rust-for-Linux/linux that referenced this pull request Feb 19, 2026
@BennoLossin @ojeda
rust: irq: add 'static bounds to irq callbacks
621609f 
These callback functions take a generic `T` that is used in the body as
the generic argument in `Registration` and `ThreadedRegistration`. Those
types require `T: 'static`, but due to a compiler bug this requirement
isn't propagated to the function. Thus add the bound. This was caught in
the upstream Rust CI [1].

[ The three errors looked similar and will start appearing with Rust
  1.95.0 (expected 2026-04-16). The first one was:

      error[E0310]: the parameter type `T` may not live long enough
      Error:    --> rust/kernel/irq/request.rs:266:43
          |
      266 |     let registration = unsafe { &*(ptr as *const Registration<T>) };
          |                                           ^^^^^^^^^^^^^^^^^^^^^^
          |                                           |
          |                                           the parameter type `T` must be valid for the static lifetime...
          |                                           ...so that the type `T` will meet its required lifetime bounds
          |
      help: consider adding an explicit lifetime bound
          |
      264 | unsafe extern "C" fn handle_irq_callback<T: Handler + 'static>(_irq: i32, ptr: *mut c_void) -> c_uint {
          |                                                     +++++++++

    - Miguel ]

Link: rust-lang/rust#149389 [1]
Signed-off-by: Benno Lossin <lossin@kernel.org>
Cc: stable@vger.kernel.org
Fixes: 29e16fc ("rust: irq: add &Device<Bound> argument to irq callbacks")
Reviewed-by: Gary Guo <gary@garyguo.net>
Reviewed-by: Daniel Almeida <daniel.almeida@collabora.com>
Acked-by: Danilo Krummrich <dakr@kernel.org>
Link: https://lore.kernel.org/rust-for-linux/20260217222425.8755-1-cole@unwrap.rs/
Link: https://patch.msgid.link/20260214092740.3201946-1-lossin@kernel.org
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
mj22226 pushed a commit to mj22226/linux that referenced this pull request Feb 28, 2026
@BennoLossin
rust: irq: add 'static bounds to irq callbacks
3851937 
[ Upstream commit 621609f ]

These callback functions take a generic `T` that is used in the body as
the generic argument in `Registration` and `ThreadedRegistration`. Those
types require `T: 'static`, but due to a compiler bug this requirement
isn't propagated to the function. Thus add the bound. This was caught in
the upstream Rust CI [1].

[ The three errors looked similar and will start appearing with Rust
  1.95.0 (expected 2026-04-16). The first one was:

      error[E0310]: the parameter type `T` may not live long enough
      Error:    --> rust/kernel/irq/request.rs:266:43
          |
      266 |     let registration = unsafe { &*(ptr as *const Registration<T>) };
          |                                           ^^^^^^^^^^^^^^^^^^^^^^
          |                                           |
          |                                           the parameter type `T` must be valid for the static lifetime...
          |                                           ...so that the type `T` will meet its required lifetime bounds
          |
      help: consider adding an explicit lifetime bound
          |
      264 | unsafe extern "C" fn handle_irq_callback<T: Handler + 'static>(_irq: i32, ptr: *mut c_void) -> c_uint {
          |                                                     +++++++++

    - Miguel ]

Link: rust-lang/rust#149389 [1]
Signed-off-by: Benno Lossin <lossin@kernel.org>
Cc: stable@vger.kernel.org
Fixes: 29e16fc ("rust: irq: add &Device<Bound> argument to irq callbacks")
Reviewed-by: Gary Guo <gary@garyguo.net>
Reviewed-by: Daniel Almeida <daniel.almeida@collabora.com>
Acked-by: Danilo Krummrich <dakr@kernel.org>
Link: https://lore.kernel.org/rust-for-linux/20260217222425.8755-1-cole@unwrap.rs/
Link: https://patch.msgid.link/20260214092740.3201946-1-lossin@kernel.org
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
johnny-mnemonic pushed a commit to linux-ia64/linux-stable-rc that referenced this pull request Mar 1, 2026
@BennoLossin
rust: irq: add 'static bounds to irq callbacks
c07cdf8 
[ Upstream commit 621609f ]

These callback functions take a generic `T` that is used in the body as
the generic argument in `Registration` and `ThreadedRegistration`. Those
types require `T: 'static`, but due to a compiler bug this requirement
isn't propagated to the function. Thus add the bound. This was caught in
the upstream Rust CI [1].

[ The three errors looked similar and will start appearing with Rust
  1.95.0 (expected 2026-04-16). The first one was:

      error[E0310]: the parameter type `T` may not live long enough
      Error:    --> rust/kernel/irq/request.rs:266:43
          |
      266 |     let registration = unsafe { &*(ptr as *const Registration<T>) };
          |                                           ^^^^^^^^^^^^^^^^^^^^^^
          |                                           |
          |                                           the parameter type `T` must be valid for the static lifetime...
          |                                           ...so that the type `T` will meet its required lifetime bounds
          |
      help: consider adding an explicit lifetime bound
          |
      264 | unsafe extern "C" fn handle_irq_callback<T: Handler + 'static>(_irq: i32, ptr: *mut c_void) -> c_uint {
          |                                                     +++++++++

    - Miguel ]

Link: rust-lang/rust#149389 [1]
Signed-off-by: Benno Lossin <lossin@kernel.org>
Cc: stable@vger.kernel.org
Fixes: 29e16fc ("rust: irq: add &Device<Bound> argument to irq callbacks")
Reviewed-by: Gary Guo <gary@garyguo.net>
Reviewed-by: Daniel Almeida <daniel.almeida@collabora.com>
Acked-by: Danilo Krummrich <dakr@kernel.org>
Link: https://lore.kernel.org/rust-for-linux/20260217222425.8755-1-cole@unwrap.rs/
Link: https://patch.msgid.link/20260214092740.3201946-1-lossin@kernel.org
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
johnny-mnemonic pushed a commit to linux-ia64/linux-stable-rc that referenced this pull request Mar 1, 2026
@BennoLossin
rust: irq: add 'static bounds to irq callbacks
44f2647 
[ Upstream commit 621609f ]

These callback functions take a generic `T` that is used in the body as
the generic argument in `Registration` and `ThreadedRegistration`. Those
types require `T: 'static`, but due to a compiler bug this requirement
isn't propagated to the function. Thus add the bound. This was caught in
the upstream Rust CI [1].

[ The three errors looked similar and will start appearing with Rust
  1.95.0 (expected 2026-04-16). The first one was:

      error[E0310]: the parameter type `T` may not live long enough
      Error:    --> rust/kernel/irq/request.rs:266:43
          |
      266 |     let registration = unsafe { &*(ptr as *const Registration<T>) };
          |                                           ^^^^^^^^^^^^^^^^^^^^^^
          |                                           |
          |                                           the parameter type `T` must be valid for the static lifetime...
          |                                           ...so that the type `T` will meet its required lifetime bounds
          |
      help: consider adding an explicit lifetime bound
          |
      264 | unsafe extern "C" fn handle_irq_callback<T: Handler + 'static>(_irq: i32, ptr: *mut c_void) -> c_uint {
          |                                                     +++++++++

    - Miguel ]

Link: rust-lang/rust#149389 [1]
Signed-off-by: Benno Lossin <lossin@kernel.org>
Cc: stable@vger.kernel.org
Fixes: 29e16fc ("rust: irq: add &Device<Bound> argument to irq callbacks")
Reviewed-by: Gary Guo <gary@garyguo.net>
Reviewed-by: Daniel Almeida <daniel.almeida@collabora.com>
Acked-by: Danilo Krummrich <dakr@kernel.org>
Link: https://lore.kernel.org/rust-for-linux/20260217222425.8755-1-cole@unwrap.rs/
Link: https://patch.msgid.link/20260214092740.3201946-1-lossin@kernel.org
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
johnny-mnemonic pushed a commit to linux-ia64/linux-stable-rc that referenced this pull request Mar 1, 2026
@BennoLossin
rust: irq: add 'static bounds to irq callbacks
ccb6b28 
[ Upstream commit 621609f ]

These callback functions take a generic `T` that is used in the body as
the generic argument in `Registration` and `ThreadedRegistration`. Those
types require `T: 'static`, but due to a compiler bug this requirement
isn't propagated to the function. Thus add the bound. This was caught in
the upstream Rust CI [1].

[ The three errors looked similar and will start appearing with Rust
  1.95.0 (expected 2026-04-16). The first one was:

      error[E0310]: the parameter type `T` may not live long enough
      Error:    --> rust/kernel/irq/request.rs:266:43
          |
      266 |     let registration = unsafe { &*(ptr as *const Registration<T>) };
          |                                           ^^^^^^^^^^^^^^^^^^^^^^
          |                                           |
          |                                           the parameter type `T` must be valid for the static lifetime...
          |                                           ...so that the type `T` will meet its required lifetime bounds
          |
      help: consider adding an explicit lifetime bound
          |
      264 | unsafe extern "C" fn handle_irq_callback<T: Handler + 'static>(_irq: i32, ptr: *mut c_void) -> c_uint {
          |                                                     +++++++++

    - Miguel ]

Link: rust-lang/rust#149389 [1]
Signed-off-by: Benno Lossin <lossin@kernel.org>
Cc: stable@vger.kernel.org
Fixes: 29e16fc ("rust: irq: add &Device<Bound> argument to irq callbacks")
Reviewed-by: Gary Guo <gary@garyguo.net>
Reviewed-by: Daniel Almeida <daniel.almeida@collabora.com>
Acked-by: Danilo Krummrich <dakr@kernel.org>
Link: https://lore.kernel.org/rust-for-linux/20260217222425.8755-1-cole@unwrap.rs/
Link: https://patch.msgid.link/20260214092740.3201946-1-lossin@kernel.org
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
@BoxyUwU BoxyUwU mentioned this pull request Apr 2, 2026
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@BoxyUwU BoxyUwU BoxyUwU left review comments

@lcnr lcnr lcnr left review comments

@jackh726 jackh726 jackh726 left review comments

Assignees

@lcnr lcnr

Labels

A-CI Area: Our Github Actions CI A-testsuite Area: The testsuite used to check the correctness of rustc disposition-merge This issue / PR is in PFCP or FCP with a disposition to merge it. finished-final-comment-period The final comment period is finished for this PR / Issue. merged-by-bors This PR was explicitly merged by bors. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. T-types Relevant to the types team, which will review and decide on the PR/issue.

Projects

None yet

Milestone

1.95.0

Development

Successfully merging this pull request may close these issues.

Lifetime bounds of Drop aren't checked properly ignored lifetime constraints in type annotations