Skip to content

Rollup of 5 pull requests - #164773

Closed
jhpratt wants to merge 13 commits into
rust-lang:mainfrom
jhpratt:rollup-9xoY9PH
Closed

jhpratt wants to merge 13 commits into
rust-lang:mainfrom
jhpratt:rollup-9xoY9PH

Conversation

@jhpratt

@jhpratt jhpratt commented Oct 22, 2026

Copy link
Copy Markdown
Member

Successful merges:

Warning

This rollup conflicts with pending auto build #164757 and may need to be recreated if the pending build succeeds.

r? @ghost

Create a similar rollup

susitsm and others added 13 commits October 21, 2026 10:18
```
error: lifetime may not live long enough
  --> $DIR/issue-55394.rs:9:9
   |
LL |     fn new(bar: &mut Bar) -> Self {
   |                 -            ---- return type is `Foo<'2>`
   |                 |
   |                 let's call the lifetime of this reference `'1`
LL |         Foo { bar }
   |         ^^^^^^^^^^^ associated function was supposed to return data with lifetime `'2` but it is returning data with lifetime `'1`
```
…-macros, r=Zalathar

Remove `record_*` macros from the metadata encoder

Replaces `record_*` macros (`record_some_lazy`, `record_some`, `record_value`, `record_array`, `record_defaulted_array`) with `encoder.table_writer().field(index, value)` in the metadata encoder
Use 64-bit futex syscalls on RV32 Linux

Closes rust-lang#164694

This changes riscv32 Linux targets to use the `SYS_futex_time64` syscall instead of `SYS_futex` in the standard library to fix compilation after rust-lang/libc#5455.

`libc::timespec` has a `c_long` for nanoseconds on 32-bit targets right now, whereas the kernel uses `long long`. I'm not sure whether this is a problem or not?

I'm also curious whether using the time64 syscall on _all_ 32-bit targets is a desired change.

r? tgross35
…lution, r=Urgau

Include `deprecated` attributes in `rustc_resolve` intra-doc link resolution

Fixes rust-lang#164711.

Problem was that we didn't include `deprecated` attribute in the "inner" marker, so it was never processed in `rustc_resolve` and therefore couldn't be found in rustdoc intra-doc link handling.

r? @Urgau
Update outdated/incorrect unstable tracking issue links

While investigating another issue, I noticed that there were a lot of unstable features with incorrect or outdated links to their tracking issues.
…expr, r=mati865

[tiny] Properly format return type in lifetime error with backticks

```
error: lifetime may not live long enough
  --> $DIR/issue-55394.rs:9:9
   |
LL |     fn new(bar: &mut Bar) -> Self {
   |                 -            ---- return type is `Foo<'2>`
   |                 |
   |                 let's call the lifetime of this reference `'1`
LL |         Foo { bar }
   |         ^^^^^^^^^^^ associated function was supposed to return data with lifetime `'2` but it is returning data with lifetime `'1`
```
@rust-bors rust-bors Bot added the rollup A PR which is a rollup label Oct 22, 2026
@rustbot rustbot added A-meta Area: Issues & PRs about the rust-lang/rust repository itself PG-exploit-mitigations Project group: Exploit mitigations S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. labels Oct 22, 2026
@jhpratt jhpratt closed this Oct 22, 2026
@rustbot rustbot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Oct 22, 2026
@jhpratt
jhpratt deleted the rollup-9xoY9PH branch October 22, 2026 23:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-meta Area: Issues & PRs about the rust-lang/rust repository itself PG-exploit-mitigations Project group: Exploit mitigations rollup A PR which is a rollup T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants