Repository navigation
Rollup of 5 pull requests - #164773
Closed
jhpratt wants to merge 13 commits into
Closed
Rollup of 5 pull requests#164773jhpratt wants to merge 13 commits into
jhpratt wants to merge 13 commits into
Conversation
…ns using the `EncodeFrom` trait
```
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`
```
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.
Successful merges:
record_*macros from the metadata encoder #164636 (Removerecord_*macros from the metadata encoder)deprecatedattributes inrustc_resolveintra-doc link resolution #164733 (Includedeprecatedattributes inrustc_resolveintra-doc link resolution)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