-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Dedupe typeorigin #23691
Merged
Merged
Dedupe typeorigin #23691
Conversation
This file contains 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
richo
force-pushed
the
dedup-typeorigin-mergable
branch
from
March 25, 2015 05:39
6fac3a1
to
00a0fce
Compare
@@ -22,6 +22,7 @@ pub use middle::ty::IntVarValue; | |||
pub use self::freshen::TypeFreshener; | |||
pub use self::region_inference::GenericKind; | |||
|
|||
use core::fmt; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't this exported through std::fmt
as well?
LGTM, modulo nits. |
richo
force-pushed
the
dedup-typeorigin-mergable
branch
from
March 26, 2015 04:43
00a0fce
to
f5d2eba
Compare
This doesn't actually solve the issue that prompted this, at: https://github.com/rust-lang/rust/blob/master/src/librustc/session/mod.rs#L262-271 But skimming the cfg it appears that all type information has been discarded long before that point.
richo
force-pushed
the
dedup-typeorigin-mergable
branch
from
March 26, 2015 04:44
f5d2eba
to
c193fe4
Compare
Nits addressed! Thanks for that. r? @eddyb |
Thanks! @bors r+ |
📌 Commit c193fe4 has been approved by |
bors
added a commit
that referenced
this pull request
Mar 26, 2015
I've started on refactoring the error handling code to avoid the need to reparse generated errors in `span_*`, but would rather land this incrementally as one monolithic PR (and have un-fond memories of merge conflicts from various other monoliths) r? @eddyb
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I've started on refactoring the error handling code to avoid the need to reparse generated errors in
span_*
, but would rather land this incrementally as one monolithic PR (and have un-fond memories of merge conflicts from various other monoliths)r? @eddyb