Uh oh!
There was an error while loading. Please reload this page.
resolve: Fix one more ICE in import validation - #57185
Merged
Merged
Conversation
rust-highfive
commented
Dec 29, 2018
Contributor
r? @cramertj (rust_highfive has picked a reviewer for you, use r? to override) |
petrochenkov
commented
Dec 29, 2018
ContributorAuthor
Beta-nominating as a regression fix, the assert was introduced in stable Rust 1.31 (in #55884). |
petrochenkov
commented
Dec 29, 2018
ContributorAuthor
I'm glad I added all those asserts in #55884. |
cramertj
commented
Dec 29, 2018
Member
petrochenkov
commented
Dec 29, 2018
ContributorAuthor
estebank
commented
Dec 29, 2018
Contributor
r=me once travis' done |
Member
@petrochenkov lol, sorry XD -- in my defense it looked like sometihng you'd be qualified to review! |
Centril
commented
Dec 29, 2018
Contributor
@bors r=estebank |
bors
commented
Dec 29, 2018
Collaborator
📌 Commit ddb550a has been approved by |
bors
commented
Dec 30, 2018
Collaborator
bors added a commit
that referenced
this pull request
Dec 30, 2018
resolve: Fix one more ICE in import validation
So if you have an unresolved import
```rust
mod m {
use foo::bar;
}
```
error recovery will insert a special item with `Def::Err` definition into module `m`, so other things depending on `bar` won't produce extra errors.
The issue was that erroneous `bar` was overwriting legitimate `bar`s coming from globs, e.g.
```rust
mod m {
use baz::*; // imports real existing `bar`
use foo::bar;
}
```
causing some unwanted diagnostics talking about "unresolved items", and producing inconsistent resolutions like #57015.
This PR stops overwriting real successful resolutions with `Def::Err`s.
Fixes#57015bors
commented
Dec 30, 2018
Collaborator
☀️ Test successful - status-appveyor, status-travis |
bors added a commit
that referenced
this pull request
Jan 4, 2019
[beta] Rollup backports Cherry-picked: * #57053: Fix alignment for array indexing * #57181: resolve: Fix another ICE in import validation * #57185: resolve: Fix one more ICE in import validation * #57282: Wf-check the output type of a function in MIR-typeck * #55318: Ensure that Rustdoc discovers all necessary auto trait bounds * #56838: Call poly_project_and_unify_type on types that contain inference types Rolled up: * #57300: [beta] Update RLS to include 100% CPU on hover bugfix * #57301: beta: bootstrap from latest stable (1.31.1) * #57292: [BETA] Update cargo r? @ghost
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
So if you have an unresolved import
error recovery will insert a special item with
Def::Errdefinition into modulem, so other things depending onbarwon't produce extra errors.The issue was that erroneous
barwas overwriting legitimatebars coming from globs, e.g.causing some unwanted diagnostics talking about "unresolved items", and producing inconsistent resolutions like #57015.
This PR stops overwriting real successful resolutions with
Def::Errs.Fixes#57015