debuginfo: Fix issue with associated types and struct fields#21471
Merged
bors merged 1 commit intorust-lang:masterfrom Jan 23, 2015
Merged
debuginfo: Fix issue with associated types and struct fields#21471bors merged 1 commit intorust-lang:masterfrom
bors merged 1 commit intorust-lang:masterfrom
Conversation
Contributor
|
(rust_highfive has picked a reviewer for you, use r? to override) |
Member
Contributor
|
+1 This fixes the ICEs that I have been hitting |
steveklabnik
added a commit
to steveklabnik/rust
that referenced
this pull request
Jan 22, 2015
…r=alexcrichton This should fix issue rust-lang#20797 (but I don't want to close it automatically). As the actual fix is very small this would be a perfect candidate for a rollup.
lnicola
added a commit
to lnicola/rust
that referenced
this pull request
Jan 27, 2026
minor: Rustc pull update
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
This should fix issue #20797 (but I don't want to close it automatically).
As the actual fix is very small this would be a perfect candidate for a rollup.