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

[1.30 beta] Multiple applicable items in scope #54474

Closed
pietroalbini opened this issue Sep 22, 2018 · 6 comments
Closed

[1.30 beta] Multiple applicable items in scope #54474

pietroalbini opened this issue Sep 22, 2018 · 6 comments
Labels
C-bug Category: This is a bug. regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Milestone

Comments

@pietroalbini
Copy link
Member

Multiple crates are failing to build in 1.30 beta because multiple applicable items are in scope.

 error[E0034]: multiple applicable items in scope
     --> /cargo-home/registry/src/gh.neting.cc-1ecc6299db9ec823/petgraph-0.4.9/src/graph_impl/stable_graph/mod.rs:1172:19
      |
 1172 |         self.iter.find_map(|(i, node)| {
      |                   ^^^^^^^^ multiple `find_map` found
      |

cc @petrochenkov

@pietroalbini pietroalbini added I-nominated T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. regression-from-stable-to-beta Performance or correctness regression from stable to beta. C-bug Category: This is a bug. labels Sep 22, 2018
@pietroalbini pietroalbini added this to the 1.30 milestone Sep 22, 2018
@eddyb
Copy link
Member

eddyb commented Sep 22, 2018

Iterator::find_map was stabilized in 1.30 according to the docs.
cc @rust-lang/libs

@pietroalbini pietroalbini added T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. and removed T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Sep 22, 2018
@withoutboats
Copy link
Contributor

withoutboats commented Sep 22, 2018

All of these are binaries with checked in lockfiles that depend on a petgraph version ^0.4.0 (in which the error occurs), because of their lockfiles they aren't getting 0.4.13, which fixes this regression in petgraph. Not sure what our protocol here is (in terms of following up with impacted crates) but this is expected breakage.

@pkgw
Copy link
Contributor

pkgw commented Sep 23, 2018

As the author of the one of the impacted crates, opening an issue like this and tagging me seems like a good protocol. My crate is linked to the Dependabot service so I'm curious to wait and see if it will flag the update to the new petgraph as an important one.

@YaLTeR
Copy link
Contributor

YaLTeR commented Sep 23, 2018

As the author of one of the impacted repositories I appreciate this protocol a lot too. Although in this particular case my repo contains some unimportant stuff so I don't mind it breaking.

@alexcrichton
Copy link
Member

This was added in #49098 and stabilized in #53385. Unfortunately we didn't do crater runs at the time, but that's why we do it for beta!

I'll put this on the libs team triage agenda, but given that this is fixed in the most recent versions and only locked projects are getting this it's probably unlikely we'll decide to revert. That being said if anyone has difficulty upgrading please let us know!

@alexcrichton
Copy link
Member

Ok discussed during triage and we've decided to close, but again anyone please let us know if it's difficult to update!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: This is a bug. regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

6 participants