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

Name _ defined multiple times #55811

Closed
Mark-Simulacrum opened this issue Nov 9, 2018 · 1 comment · Fixed by #56117

Comments

@Mark-Simulacrum
Copy link
Member

commented Nov 9, 2018

https://crater-reports.s3.amazonaws.com/beta-1.31-1/beta-2018-10-30/reg/type_level_examples-0.0.22/log.txt, https://crates.io/crates/type_level_examples/0.0.22

error[E0428]: the name `_` is defined multiple times
Nov 02 01:29:54.935 INFO kablam!   |
Nov 02 01:29:54.935 INFO kablam!   = note: `_` must be defined only once in the type namespace of this module

This appears to ICE on nightly so maybe that's the underlying cause?

cc @petrochenkov

@petrochenkov

This comment has been minimized.

Copy link
Contributor

commented Nov 21, 2018

Fixed in #56117

bors added a commit that referenced this issue Nov 21, 2018
Auto merge of #56117 - petrochenkov:iempty, r=eddyb
resolve: Make "empty import canaries" invisible from other crates

Empty imports `use prefix::{};` are desugared into `use prefix::{self as _};` to make sure the prefix is checked for privacy/stability/etc.
This caused issues in cross-crate scenarios because gensyms are lost in crate metadata (the `_` is a gensym).

Fixes #55811
bors added a commit that referenced this issue Nov 21, 2018
Auto merge of #56117 - petrochenkov:iempty, r=eddyb
resolve: Make "empty import canaries" invisible from other crates

Empty imports `use prefix::{};` are desugared into `use prefix::{self as _};` to make sure the prefix is checked for privacy/stability/etc.
This caused issues in cross-crate scenarios because gensyms are lost in crate metadata (the `_` is a gensym).

Fixes #55811

@bors bors closed this in #56117 Nov 21, 2018

@alexcrichton alexcrichton moved this from Triaged to Backport in progress in 1.31 regressions Nov 21, 2018

@alexcrichton alexcrichton moved this from Backport in progress to Fixed in 1.31 regressions Nov 23, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
3 participants
You can’t perform that action at this time.