Skip to content

Type error messages have typedefs expanded away #4374

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

Closed
catamorphism opened this issue Jan 8, 2013 · 5 comments
Closed

Type error messages have typedefs expanded away #4374

catamorphism opened this issue Jan 8, 2013 · 5 comments
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc

Comments

@catamorphism
Copy link
Contributor

These are all in compile-fail. Presumably due to @pcwalton 's recent commits.

@ghost ghost assigned pcwalton Jan 8, 2013
@catamorphism
Copy link
Contributor Author

Not critical for 0.6, de-milestoning

@catamorphism
Copy link
Contributor Author

unsafe-fn-autoderef was easy to update -- I filed #6482 . The other two still fail because type error messages print types with synonyms expanded away. I'm not sure how important it is to preserve type synonyms in error messages. It can certainly make error messages more readable sometimes.

I guess I'll nominate for milestone 5, production-ready, so we can discuss it; also will change the bug title to something more descriptive.

@graydon
Copy link
Contributor

graydon commented May 16, 2013

just a bug, removing milestone/nomination.

@catamorphism
Copy link
Contributor Author

Visiting for triage. Still important.

@catamorphism
Copy link
Contributor Author

I can't figure out which test cases were affected here, and grepping for "4374" in the repo doesn't turn up anything, so I'm closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc
Projects
None yet
Development

No branches or pull requests

3 participants