-
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 5 pull requests #57590
Rollup of 5 pull requests #57590
Conversation
Use the `collect_and_partition_mono_items ` query to avoid calling the collector
This function has no side effects, and its result is ignored.
Include the kind of the binding that we're suggesting, and use a structured suggestion.
It requires an unreachable IP address, but there is no such thing, and this has caused it to fail for multiple people. Fixes rust-lang#44698, fixes rust-lang#50065.
@bors r+ p=5 |
📌 Commit 77ef320eb1a48541286687ed0c795d1761c54683 has been approved by |
⌛ Testing commit 77ef320eb1a48541286687ed0c795d1761c54683 with merge fb9c5fd8d65413eb553e61f0485de479401a71ce... |
💔 Test failed - checks-travis |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
93857dc
to
1d029c6
Compare
…oerister Parallelize and optimize parts of HIR map creation r? @michaelwoerister
…ster MetadataOnlyCodegenBackend: run the collector only once Use the `collect_and_partition_mono_items` query to avoid calling the collector directly twice. Fixes rust-lang#57406.
…dor, r=joshtriplett,Centril Stabilize cfg_target_vendor This stabilizes the use of `cfg(target_vendor = "...")` and removes the corresponding `cfg_target_vendor` feature. Other unstable cfgs remain behind their existing feature gates. This functionality was added back in 2015 in rust-lang#28612 to complete the coverage of target tuples (`<arch><sub>-<vendor>-<os>-<env>`). [RFC 131](https://github.com/rust-lang/rfcs/blob/master/text/0131-target-specification.md) governs the target specification, not including `target_vendor` seems to have just been an oversight. `target_os`, `target_family`, and `target_arch` are stable as of 1.0.0. `target_env` was also not mentioned in RFC 131, was added in rust-lang#24777, never behind a feature_gate, and insta-stable at 1.1.0. The functionality is tested in [test/run-pass/cfg/cfg-target-vendor.rs](https://github.com/rust-lang/rust/blob/master/src/test/run-pass/cfg/cfg-target-vendor.rs). Closes rust-lang#29718
…ckmdavis clarify resolve typo suggestion Include the kind of the binding that we're suggesting, and use a structured suggestion. Fixes rust-lang#53445.
privacy: Fix private-in-public check for existential types Fixes rust-lang#53546 (regression from rust-lang#56878) r? @arielb1
…utable, r=sfackler Remove the `connect_timeout_unroutable` test. It requires an unreachable IP address, but there is no such thing, and this has caused it to fail for multiple people. Fixes rust-lang#44698, fixes rust-lang#50065. r? @sfackler
Your PR failed on Travis (raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem. Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Successful merges:
connect_timeout_unroutable
test. #57584 (Remove theconnect_timeout_unroutable
test.)Failed merges:
r? @ghost