{"issue":{"user":{"id":340349,"login":"msullivan","url":"https://api.github.com/users/msullivan","avatar_url":"https://secure.gravatar.com/avatar/8c31c51fe9e8014c78d3c7d7e214484c?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"8c31c51fe9e8014c78d3c7d7e214484c"},"milestone":null,"title":"Typechecker error messages don't use type abbreviations","created_at":"2011-08-16T23:09:50Z","labels":[{"name":"feature","url":"https://api.github.com/repos/graydon/rust/labels/feature","color":"d912e0"},{"name":"typeck","url":"https://api.github.com/repos/graydon/rust/labels/typeck","color":"C8C8A9"}],"state":"open","updated_at":"2011-12-21T21:53:51Z","id":1419310,"html_url":"https://github.com/graydon/rust/issues/828","closed_at":null,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"body":"Since we got rid of cnames (for good reason, as I understand it), typechecker error messages always use the full structural types, which is sucky. Patrick says he has a plan for fixing this that isn't high priority right now. Creating this bug to track.\r\n\r\nWe probably want this fixed for a release?","number":828,"url":"https://api.github.com/repos/graydon/rust/issues/828","comments":10,"assignee":{"id":157897,"login":"pcwalton","url":"https://api.github.com/users/pcwalton","avatar_url":"https://secure.gravatar.com/avatar/eb3ddcfd60478e22ac5196f800fecf48?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"eb3ddcfd60478e22ac5196f800fecf48"}},"comment":{"user":{"id":155238,"login":"nikomatsakis","url":"https://api.github.com/users/nikomatsakis","avatar_url":"https://secure.gravatar.com/avatar/8f9e4181f2951ca8f21ed5c541686367?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"8f9e4181f2951ca8f21ed5c541686367"},"created_at":"2011-12-21T21:53:51Z","updated_at":"2011-12-21T21:53:51Z","id":3240199,"body":"All that said, I know I am complaining a lot, but ultimately I am not completely opposed to this fix, although I am not persuaded it's the best approach for the reasons I enumerated.  Still, almost anything is better than the current situation, as long as it's not buggy..","url":"https://api.github.com/repos/graydon/rust/issues/comments/3240199"},"action":"created"}