-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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 6 pull requests #129162
Rollup of 6 pull requests #129162
Conversation
…o `run-make` tests
…r=compiler-errors Re-enable more debuginfo tests on freebsd These ignores are _ancient_, we don't run freebsd tests in CI, and even if we did they'd probably pass because the test suite passes with the latest gdb release on Linux.
Special-case alias ty during the delayed bug emission in `try_from_lit` This PR tries to fix rust-lang#116308. A delayed bug in `try_from_lit` will not be emitted so that the compiler will not ICE when it sees the pair `(ast::LitKind::Int, ty::TyKind::Alias)` in `lit_to_const` (called from `try_from_lit`). This PR is related to an unstable feature `adt_const_params` (rust-lang#95174). r? ``@BoxyUwU``
Stabilize `is_none_or` Closes: rust-lang#126383. `@rustbot` label: +T-libs-api r? libs-api
…pt, r=jieyouxu Migrate `validate_json.py` script to rust in `run-make/rustdoc-map-file` test This PR fixes the FIXME I added for future-me who become present-me. :') Since there are multiple `run-make` tests using python scripts, I suppose more of them will migrate to Rust, hence why I added the `jzon` public reexport to the `run-make-support` crate. cc `@jieyouxu` r? `@Kobzol`
Fix wrong source location for some incorrect macro definitions Fixes rust-lang#95463 Currently the code will consume the next token tree after `var` when trying to parse `$var:some_type` even when it's not a `:` (e.g. a `$` when input is `($foo $bar:tt) => {}`). Additionally it will return the wrong span when it's not a `:`. This PR fixes these problems.
Stabilize std::thread::Builder::spawn_unchecked Closes rust-lang#55132.
@bors r+ rollup=never p=6 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: 569d7e3d15 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (506052d): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results (primary -1.5%, secondary -3.7%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 750.018s -> 750.072s (0.01%) |
Successful merges:
try_from_lit
#129042 (Special-case alias ty during the delayed bug emission intry_from_lit
)is_none_or
#129086 (Stabilizeis_none_or
)validate_json.py
script to rust inrun-make/rustdoc-map-file
test #129149 (Migratevalidate_json.py
script to rust inrun-make/rustdoc-map-file
test)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup