More specific errors for kind check failures #12201

Activity

1. nikomatsakis

   added

   E-mentor

   on Feb 12, 2014
2. nikomatsakis commented on Feb 12, 2014

   

   nikomatsakis

   on Feb 12, 2014

   ContributorAuthor

   More actions

   This was discussed some on IRC. To clarify the consensus, the basic strategy we had in mind is to:

   1. Refactor TypeContents into a visitor that walks the, well, type contents.
   2. TypeContents uses this visitor to compute its bitsets.
   3. In the case of an error, a separate path of code uses the visitor to walk down and compute a "path" from the type to the smallest error case. Something like "this is not send because x.y.z is not sendable". This path probably has the same form as the paths that the borrow checker reports, though it may not use the same data structures.

   The reason for this approach is that we do not want to compute nor store the full paths in the normal case, since TypeContents are computed for a LOT of types, and only a very few of them have errors.
3. flaper87

   self-assigned this

   on Mar 24, 2014
4. nikomatsakis

   unassigned

   flaper87

   on Jun 16, 2014
5. nikomatsakis commented on Jan 16, 2015

   

   nikomatsakis

   on Jan 16, 2015

   ContributorAuthor

   More actions

   @flaper87 did this as part of the OIBIT work.
6. nikomatsakis

   closed this as completedon Jan 16, 2015
7. bors

   added a commit that references this issue on Jul 25, 2022

   Auto merge of rust-lang#12201 - Veykril:inlay-hide, r=Veykril

   ...

   cf152e8