-
Notifications
You must be signed in to change notification settings - Fork 13.4k
ICE - importing a module twice, once via glob #25763
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
Labels
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
Comments
barosl
added a commit
to barosl/rust
that referenced
this issue
May 26, 2015
Currently, for `use` declarations with multiple paths, only the `use` item itself is saved in the AST map, not the individual path nodes. This can lead to a problem when a span of a specific path node is needed. For example, rust-lang#24818 caused an ICE because of this, in `ImportResolver::check_for_conflicting_import()`. Fixes rust-lang#25763.
barosl
added a commit
to barosl/rust
that referenced
this issue
May 26, 2015
Currently, for `use` declarations with multiple paths, only the `use` item itself is saved in the AST map, not the individual path nodes. This can lead to a problem when a span of a specific path node is needed. For example, rust-lang#24818 caused an ICE because of this, in `ImportResolver::check_for_conflicting_import()`. Fixes rust-lang#25763.
bors
added a commit
that referenced
this issue
May 27, 2015
Currently, for `use` declarations with multiple paths, only the `use` item itself is saved in the AST map, not the individual path nodes. This can lead to a problem when a span of a specific path node is needed. For example, #24818 caused an ICE because of this, in `ImportResolver::check_for_conflicting_import()`. Fixes #25763.
XMPPwocky
pushed a commit
to XMPPwocky/rust
that referenced
this issue
May 29, 2015
Currently, for `use` declarations with multiple paths, only the `use` item itself is saved in the AST map, not the individual path nodes. This can lead to a problem when a span of a specific path node is needed. For example, rust-lang#24818 caused an ICE because of this, in `ImportResolver::check_for_conflicting_import()`. Fixes rust-lang#25763.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This only appears to occur in nightly (1.2.0-dev). The playpen has no issues for stable or beta.
Reproduction
Output
Meta
The text was updated successfully, but these errors were encountered: