Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upTurn sufficiently old compatibility lints into hard errors #42136
Conversation
rust-highfive
assigned
nikomatsakis
May 21, 2017
petrochenkov
added
S-waiting-on-crater
S-waiting-on-review
labels
May 21, 2017
This comment has been minimized.
This comment has been minimized.
|
Started crater run:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Primary problems are petgraph and typemap, though there are a few others.
Legitimate failures:
False positives:
|
This comment has been minimized.
This comment has been minimized.
|
This is interesting, all the affected crates (except for abandoned |
This comment has been minimized.
This comment has been minimized.
Yeah, this is a common scenario. Frustrating. I'm not sure what's the best fix. Another option is to encourage the crate authors to push a new minor version that fixes the lint; we have done that in the past for major cases. |
This was referenced May 25, 2017
This comment has been minimized.
This comment has been minimized.
|
|
This was referenced May 26, 2017
This comment has been minimized.
This comment has been minimized.
|
cc @rust-lang/compiler @alexcrichton @brson -- so what should we do here? There are a number of outdated dependencies in crater which means that if we "close the door" on these compatibility lints, they will break. One option:
Seems like pinging authors is a good first step! |
This comment has been minimized.
This comment has been minimized.
I've already submitted PRs to all affected crates except for those depending on |
This comment has been minimized.
This comment has been minimized.
|
Thanks for the legwork here sending PRs @petrochenkov! It sounds like the major sources of breakage are or are about to all be mitigated? In that sense maybe leave |
petrochenkov
force-pushed the
petrochenkov:oldhard
branch
from
7df86e4
to
414f78c
May 26, 2017
This comment has been minimized.
This comment has been minimized.
Done. |
This comment has been minimized.
This comment has been minimized.
|
@petrochenkov @nikomatsakis Does this need another crater run? The status tag wasn't removed after the last one and I'm not clear on the current status based on discussion. |
This comment has been minimized.
This comment has been minimized.
|
@Mark-Simulacrum |
This comment has been minimized.
This comment has been minimized.
|
I'm a little confused by that; if we land this now, before the PRs are merged and published, presumably that would still break the ecosystem? Or am I missing something? |
This comment has been minimized.
This comment has been minimized.
|
@Mark-Simulacrum |
This comment has been minimized.
This comment has been minimized.
|
Ah, okay. Wasn't sure about the actual impact of these changes. |
This comment has been minimized.
This comment has been minimized.
|
|
nikomatsakis
removed
the
S-waiting-on-crater
label
May 30, 2017
This comment has been minimized.
This comment has been minimized.
|
r=me once rebased |
This comment has been minimized.
This comment has been minimized.
|
@petrochenkov for future tracking purposes if you've still got links to the PRs to fix upstream crates, mind throwing them into the PR description? That way if we see regressions crop up on crater we can quickly find the upstream PR to fix it. |
petrochenkov
added some commits
May 21, 2017
petrochenkov
force-pushed the
petrochenkov:oldhard
branch
from
414f78c
to
26d5c0e
May 30, 2017
This comment has been minimized.
This comment has been minimized.
|
@bors r=nikomatsakis |
This comment has been minimized.
This comment has been minimized.
|
|
This comment has been minimized.
This comment has been minimized.
bors
added a commit
that referenced
this pull request
Jun 1, 2017
This comment has been minimized.
This comment has been minimized.
|
|
This comment has been minimized.
This comment has been minimized.
|
Error looks potentially spurious, but hard to tell. @bors retry
|
frewsxcv
added a commit
to frewsxcv/rust
that referenced
this pull request
Jun 1, 2017
This comment has been minimized.
This comment has been minimized.
|
My guess is #33434 |
bors
added a commit
that referenced
this pull request
Jun 1, 2017
bors
merged commit 26d5c0e
into
rust-lang:master
Jun 1, 2017
This was referenced Jun 1, 2017
brson
added
the
relnotes
label
Jun 1, 2017
brson
referenced this pull request
Jun 6, 2017
Closed
Rust 1.19 regression, 0.1.8, variant is private and cannot be reexported in pub glob #42460
This comment has been minimized.
This comment has been minimized.
|
We're probably going to need writeups of all these for the release notes. |
petrochenkov commentedMay 21, 2017
•
edited
It's been almost 7 months since #36894 was merged, so it's time to take the next step.
[breaking-change], needs crater run.
PRs/issues submitted to affected crates:
gnzlbg/ctest#17
Sean1708/rusty-cheddar#55
m-r-r/helianto#3
azdle/virgil#1
rust-locale/rust-locale#24
mneumann/acyclic-network-rs#1
reem/rust-typemap#38
cc https://internals.rust-lang.org/t/moving-forward-on-forward-compatibility-lints/4204
cc #34537 #36887
Closes #36886
Closes #36888
Closes #36890
Closes #36891
Closes #36892
r? @nikomatsakis