-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
Rollup of 7 pull requests #123010
Rollup of 7 pull requests #123010
Commits on Mar 18, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 56e152d - Browse repository at this point
Copy the full SHA 56e152dView commit details
Commits on Mar 22, 2024
-
fix(bootstrap/dist): use versioned dirs when vendoring
Currently, if you attempt to run ui tests in a vendored build, you will see this failure ``` ---- [ui] tests/ui/issues/issue-21763.rs stdout ---- diff of stderr: 8 = note: required because it appears within the type `(Rc<()>, Rc<()>)` 9 = note: required for `hashbrown::raw::RawTable<(Rc<()>, Rc<()>)>` to implement `Send` 10 note: required because it appears within the type `hashbrown::map::HashMap<Rc<()>, Rc<()>, RandomState>` - --> $HASHBROWN_SRC_LOCATION + --> /rust/deps/hashbrown/src/map.rs:190:12 12 note: required because it appears within the type `HashMap<Rc<()>, Rc<()>>` 13 --> $SRC_DIR/std/src/collections/hash/map.rs:LL:COL 14 note: required by a bound in `foo` ``` This happend because the code that attempts to remap `HASHBROWN_SRC_LOCATION` expects it to be under `hashbrown-$version`, which is the case in a normal cargo registry, but not when vendor, where by default crates may not have the version in their directory name. This change passes `--versioned-dirs` to `cargo vendor` to enforce that every crate includes the version in the subdir name, which fixes the ui test and brings `--enable-vendor` builds closer to normal ones.
Configuration menu - View commit details
-
Copy full SHA for 25d0601 - Browse repository at this point
Copy the full SHA 25d0601View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9685161 - Browse repository at this point
Copy the full SHA 9685161View commit details
Commits on Mar 23, 2024
-
Configuration menu - View commit details
-
Copy full SHA for d3fc623 - Browse repository at this point
Copy the full SHA d3fc623View commit details
Commits on Mar 24, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 87808e7 - Browse repository at this point
Copy the full SHA 87808e7View commit details -
CFI: Handle dyn with no principal
In user-facing Rust, `dyn` always has at least one predicate following it. Unfortunately, because we filter out marker traits from receivers at callsites and `dyn Sync` is, for example, legal, this results in us having `dyn` types with no predicates on occasion in our alias set encoding. This patch handles cases where there are no predicates in a `dyn` type which are relevant to its alias set. Fixes rust-lang#122998
Configuration menu - View commit details
-
Copy full SHA for ea45185 - Browse repository at this point
Copy the full SHA ea45185View commit details -
In
pretty_print_type()
, printasync fn
futures' paths instead of ……spans. This makes `-Zprint-type-sizes`'s output easier to read, because the name of an `async fn` is more immediately recognizable than its span. I also deleted the comment "FIXME(eddyb) should use `def_span`." because it appears to have already been fixed by commit 67727aa.
Configuration menu - View commit details
-
Copy full SHA for aaf49b4 - Browse repository at this point
Copy the full SHA aaf49b4View commit details -
Rollup merge of rust-lang#120557 - n8henrie:issue_120553, r=Mark-Simu…
…lacrum Add rust-lldb pretty printing for Path and PathBuf Fixes rust-lang#120553 Fixes rust-lang#48462
Configuration menu - View commit details
-
Copy full SHA for 1c6131f - Browse repository at this point
Copy the full SHA 1c6131fView commit details -
Rollup merge of rust-lang#121051 - Nilstrieb:targetting, r=davidtwco,…
…onur-ozkan Introduce infrastructure for generating target docs See rust-lang#120745 It's highly unlikely that the format is optimal, but it's okay at least and can always be improved. Mostly posting this to get something working so we can continue. Use `TARGET_CHECK_ONLY=0` to actually build the book instead of just checking the new docs. r? ``@davidtwco``
Configuration menu - View commit details
-
Copy full SHA for 731e337 - Browse repository at this point
Copy the full SHA 731e337View commit details -
Rollup merge of rust-lang#122892 - lovesegfault:versioned-vendor, r=o…
…nur-ozkan fix(bootstrap/dist): use versioned dirs when vendoring Currently, if you attempt to run ui tests in a vendored build, you will see this failure ``` ---- [ui] tests/ui/issues/issue-21763.rs stdout ---- diff of stderr: 8 = note: required because it appears within the type `(Rc<()>, Rc<()>)` 9 = note: required for `hashbrown::raw::RawTable<(Rc<()>, Rc<()>)>` to implement `Send` 10 note: required because it appears within the type `hashbrown::map::HashMap<Rc<()>, Rc<()>, RandomState>` - --> $HASHBROWN_SRC_LOCATION + --> /rust/deps/hashbrown/src/map.rs:190:12 12 note: required because it appears within the type `HashMap<Rc<()>, Rc<()>>` 13 --> $SRC_DIR/std/src/collections/hash/map.rs:LL:COL 14 note: required by a bound in `foo` ``` This happens because the code that attempts to remap `HASHBROWN_SRC_LOCATION` expects it to be under `hashbrown-$version`, which is the case in a normal cargo registry, but not when vendoring, where by default crates may not have the version in their directory name. This change passes `--versioned-dirs` to `cargo vendor` to enforce that every crate includes the version in the subdir name, which fixes the ui test and brings `--enable-vendor` builds closer to normal ones.
Configuration menu - View commit details
-
Copy full SHA for 1f25171 - Browse repository at this point
Copy the full SHA 1f25171View commit details -
Rollup merge of rust-lang#122896 - dpaoliello:stdarch, r=Amanieu
Update stdarch submodule r? `@Amanieu`
Configuration menu - View commit details
-
Copy full SHA for b35a9c2 - Browse repository at this point
Copy the full SHA b35a9c2View commit details -
Rollup merge of rust-lang#122923 - kpreid:print-async-def, r=compiler…
…-errors In `pretty_print_type()`, print `async fn` futures' paths instead of spans. This makes `-Zprint-type-sizes`'s output easier to read, because the name of an `async fn` is more immediately recognizable than its span. This change will also synergize with my other `-Zprint-type-sizes` PR rust-lang#122922 which prints the type of child futures being awaited. I also deleted the comment "FIXME(eddyb) should use `def_span`." because it appears to have already been fixed by commit 67727aa.
Configuration menu - View commit details
-
Copy full SHA for 1992f2f - Browse repository at this point
Copy the full SHA 1992f2fView commit details -
Rollup merge of rust-lang#122970 - cuviper:use-chunk_by, r=Mark-Simul…
…acrum Use `chunk_by` when building `ReverseSccGraph` With stable `chunk_by` in Rust 1.77, this code doesn't need `Itertools::group_by` anymore.
Configuration menu - View commit details
-
Copy full SHA for 4f9ab98 - Browse repository at this point
Copy the full SHA 4f9ab98View commit details -
Rollup merge of rust-lang#123003 - maurer:dyn-empty, r=compiler-errors
CFI: Handle dyn with no principal In user-facing Rust, `dyn` always has at least one predicate following it. Unfortunately, because we filter out marker traits from receivers at callsites and `dyn Sync` is, for example, legal, this results in us having `dyn` types with no predicates on occasion in our alias set encoding. This patch handles cases where there are no predicates in a `dyn` type which are relevant to its alias set. Fixes rust-lang#122998 r? workingjubilee
Configuration menu - View commit details
-
Copy full SHA for 3014ac3 - Browse repository at this point
Copy the full SHA 3014ac3View commit details