mozilla/rust — Issue #1507: Improve type error messages
Author: marijnh
Created: 2012-01-13 20:03:48+00:00
State: open

- The type errors sometimes fall back to the nameless (unpacked) names for named types. This is especially awkward for tags and such, where it uses metadata::tyencode to produce a (mostly unreadable) string. Find out why it doesn't see the type's proper name.

- Module-qualify the names of types when printed, so you don't get "expected 't' but found 't'"

- Finally store names for native types ("expected native but found native")