I understand that. I just don't understand why calling getTypeImpl on a type 
gives you a different tree from the one that getImpl on a symbol returns. I 
would've thought that the latter would simply delegate the job to the former 
when the symbol is associated with a type. Is there some semantic sense behind 
it, or is it just an implementation quirk?

Reply via email to