-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
add coherence future-compat warnings for marker-only trait objects #56481
Conversation
59fde36
to
e24cd91
Compare
A crater run would be nice. cc @Mark-Simulacrum ? |
@rust-lang/infra Could we get a crater run on this branch? check-only should be fine - I just want to see when my lint will fire. |
@bors try |
@bors are you still there? |
@bors try please |
⌛ Trying commit e24cd91 with merge cd9f7376b6b24f6a277b46070935c4cb83606e90... |
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 |
please don't try this until travis is green! |
49128bc
to
35919bd
Compare
@bors try |
add coherence future-compat warnings for marker-only trait objects The future-compat warnings break code that assumes that `dyn Send + Sync != dyn Sync + Send`, and are the first step in making them equal. cc #33140. Note: this lint should be made to default-warn before we merge. It is deny only for the crater run. r? @nikomatsakis / @scalexm . cc @Centril & @alexreg.
☀️ Test successful - status-travis |
@craterbot run start=master#c8ae2de8363be088604ffa2ccba84ff7ad7250bc end=try#1df97983eb2057dc6a8f7eb364e263b51ae23230 mode=check-only |
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🎉 Experiment
|
@rust-lang/lang meeting says -- seems like we should clearly go forward. |
The future-compat warnings break code that assumes that `dyn Send + Sync != dyn Sync + Send`, and are the first step in making them equal. cc rust-lang#33140. It should be possible to revert this commit when we're done with the warnings.
35919bd
to
c2ba2a7
Compare
rebased. However, should we just directly go to an hard error? |
@bors r+ |
📌 Commit f934cfc has been approved by |
I guess for now we can land this version, it'd be nice to do at least a short warning period, though I'd definitely like to land #56837 ASAP |
add coherence future-compat warnings for marker-only trait objects The future-compat warnings break code that assumes that `dyn Send + Sync != dyn Sync + Send`, and are the first step in making them equal. cc #33140. Note: this lint should be made to default-warn before we merge. It is deny only for the crater run. r? @nikomatsakis / @scalexm . cc @Centril & @alexreg.
☀️ Test successful - status-appveyor, status-travis |
It seems we went for deny-by-default here instead of warn; was that intentional? cc @nikomatsakis |
It wasn't intentional - I forgot to change it to warn after I made a crater run. However, I think the only affected crate is |
@arielb1 My concern isn't so much |
Having a deny-by-default lint shouldn't affect reverse dependencies. |
@arielb1 Okay. Should I change it to warn-by-default anyway? |
…akis Add support for trait-objects without a principal The hard-error version of #56481 - should be merged after we do something about the `traitobject` crate. Fixes #33140. Fixes #57057. r? @nikomatsakis
The future-compat warnings break code that assumes that
dyn Send + Sync != dyn Sync + Send
, and are the first step in making them equal. cc #33140.Note: this lint should be made to default-warn before we merge. It is deny only for the crater run.
r? @nikomatsakis / @scalexm . cc @Centril & @alexreg.