Skip to content
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 12 pull requests #77509

Closed
wants to merge 41 commits into from
Closed

Rollup of 12 pull requests #77509

wants to merge 41 commits into from

Conversation

jonas-schievink
Copy link
Contributor

Successful merges:

Failed merges:

r? @ghost

dlrobertson and others added 30 commits September 18, 2020 13:08
 - Allow c-variadic associated functions
 - Add test for c-variadic functions in the Impl context
Remove trailing `-`.
The previous error was confusing since it made it sound like you can't
link to items that are defined outside the current module.

Also suggested importing the item.
The new error was confusing when there was partial resolution (something
like `std::io::nonexistent`); the old one is better for those cases.
This matches Cargo behavior and avoids the (somewhat expensive) double checking,
as well as the unfortunate duplicate error messages (#76822,
rust-lang/cargo#5128).
This makes it easier to make rapid changes without having to constantly
fix warnings.
rustc_ast_passes: allow c-variadic associated fns

 - Allow c-variadic associated functions
 - Add test for c-variadic functions in the Impl context

Related To: #44930
CC: @jethrogb @sarvi
r? @joshtriplett
Use `tracing` spans to trace the entire MIR interp stack

r? @RalfJung

While being very verbose, this allows really good tracking of what's going on. While I considered schemes like the previous indenter that we had (which we could get by using the `tracing-tree` crate), this will break down horribly with things like multithreaded rustc. Instead, we can now use `RUSTC_LOG` to restrict the things being traced. You could specify a filter in a way that only shows the logging of a specific frame.

![screenshot of command line output of the new formatting](https://user-images.githubusercontent.com/332036/89291343-aa40de00-d65a-11ea-9f6c-ea06c1806327.png)

If we lower the span's level to `debug`, then in `info` level logging we'd not see the frames, but in `debug` level we would see them. The filtering rules in `tracing` are super powerful, but  I'm not sure if we can specify a filter so we do see `debug` level events, but *not* the `frame` spans. The documentation at https://docs.rs/tracing-subscriber/0.2.10/tracing_subscriber/struct.EnvFilter.html makes me think that we can only turn on things, not turn off things at a more precise level.

cc @hawkw
Uplift drop-bounds lint from clippy

Bounds on `T: Drop` do nothing, so they should warn.
updated p! macro to accept literals

Closes #70948

Huge thanks @eddyb for helping me out!
Add some regression tests

Closes #66501
Closes #68951
Closes #72565
Closes #74244
Closes #75299

The first issue is fixed in 1.43.0, other issues are fixed in the recent nightly.
BTreeMap: complete the compile-time test_variance test case

Some of the items added to the new `test_sync` belonged in the old `test_variance` as well. And fixed inconsistent paths to nearby modules.
r? @Mark-Simulacrum
…yn514

Improve rustdoc error for failed intra-doc link resolution

The previous error was confusing since it made it sound like you can't
link to items that are defined outside the current module.

Also suggested importing the item.

r? @jyn514
Make --all-targets in x.py check opt-in

In particular due to #76822, making this the default is currently suboptimal.

r? @ecstatic-morse
Set `deny-warnings = false` in contributor defaults

This makes it easier to make rapid changes without having to constantly
fix warnings.
Support vectors with fewer than 8 elements for simd_select_bitmask

Resolves the issue raised here: rust-lang/stdarch#310 (comment)
@jonas-schievink
Copy link
Contributor Author

@bors r+ rollup=never p=12

@rustbot modify labels: rollup

@bors
Copy link
Contributor

bors commented Oct 3, 2020

📌 Commit 5efe9be has been approved by jonas-schievink

@rustbot rustbot added the rollup A PR which is a rollup label Oct 3, 2020
@bors bors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Oct 3, 2020
@bors
Copy link
Contributor

bors commented Oct 3, 2020

⌛ Testing commit 5efe9be with merge 42f52601824eae3fd8ffa6e6e58e12e5473d76c0...

@bors
Copy link
Contributor

bors commented Oct 3, 2020

💔 Test failed - checks-actions

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Oct 3, 2020
@jonas-schievink jonas-schievink deleted the rollup-w0wqywa branch October 3, 2020 23:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rollup A PR which is a rollup S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.