-
Notifications
You must be signed in to change notification settings - Fork 13k
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 #135678
Rollup of 6 pull requests #135678
Conversation
This makes tidy warn on the presence of any directives it does not recognize. There are changes in compiletest because that file used "tidy-alphabet" instead of "tidy-alphabetical".
for now, only builtin `Sized` impls are tracked as being `Trivial`
…ompiler-errors cleanup promoteds move check r? types
…ozkan Make tidy warn on unrecognized directives This PR makes it so tidy warns on unrecognized directives, as recommended on [the discussion of rust-lang#130984](rust-lang#130984 (comment)). This is edited from the previous version of this PR, which only warned on "tidy-ignore" and no other tidy directive typos. Fixes rust-lang#130984. ``@rustbot`` label A-tidy C-enhancement
…rash, r=oli-obk Remove unnecessary assertion for reference error Fixes rust-lang#135341 From comment: rust-lang#135341 (comment) r? ``@oli-obk``
…=Kobzol ci: improve github action name
new solver: prefer trivial builtin impls As discussed [on zulip](https://rust-lang.zulipchat.com/#narrow/channel/364551-t-types.2Ftrait-system-refactor/topic/needs_help.3A.20trivial.20builtin.20impls), this PR: - adds a new `BuiltinImplSource::Trivial` source, and marks the `Sized` builtin impls as trivial - prefers these trivial builtin impls in `merge_trait_candidates` The comments can likely be wordsmithed a bit better, and I ~stole~ was inspired by the old solver ones. Let me know how you want them improved. When enabling the new solver for tests, 3 UI tests now pass: - `regions/issue-26448-1.rs` and its sibling `regions/issue-26448-2.rs` were rejected by the new solver but accepted by the old one - and `issues/issue-42796.rs` where the old solver emitted some overflow errors in addition to the expected error (For some reason one of these tests is run-pass, but I can take care of that another day) r? lcnr
…nur-ozkan add src/librustdoc and src/rustdoc-json-types to RUSTC_IF_UNCHANGED_ALLOWED_PATHS fixes rust-lang#135650 r? ``@onur-ozkan``
@bors r+ rollup=never p=6 |
🌲 The tree is currently closed for pull requests below priority 100. This pull request will be tested once the tree is reopened. |
matthias: the fuchsia fix #135675 should land in a couple hours, if you're online then, that should unblock CI and the tree can be reopened (I believe that I will not be online then, but can keep an eye on it from my phone 😅 ) |
yeh I saw that, can take care of reopening the tree :) |
@bors treeclosed- |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: bd62a452f4 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (8321f00): 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 -2.5%, secondary -1.9%)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.
CyclesResults (secondary 3.1%)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.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 764.994s -> 763.514s (-0.19%) |
Successful merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup