Super classes and interfaces of annotated classes should also be reflectable. about reflectable.dart

[eernstg]

I think that it is reasonable to say that it is already covered. The inclusion of otherwise-not-reflectable superclasses is implied by typeRelationsCapability, because that capability subsumes the superClassCapability (which never existed, but it is implicitly present on p.7 in Fig.1 in the capability design document, and is then later unified with others into typeRelationsCapability).

Granted, it's not the same thing to promise that superclass can be used on a ClassMirror, and promising that the set of reflectable classes will be upwards closed (i.e., that all direct and indirect superclasses of reflectable classes will also be considered reflectable). However, it has essentially a zero cost to support the use of the superclass method among class mirrors for a given set of reflectable classes, whereas the upward-closure may have a substantial cost (because it can make many additional classes reflectable, and each of them has many features).

Based on this, I'll go for a model where upward-closure of the set of reflectable classes is part of the semantics of typeRelations. If needed, we can still split capabilities into more fine-grained ones, and reinterpret the more coarse-grained ones as 'grouping tokens' (p10 in the design document).

I'm currently implementing this. Note that many other parts of typeRelations are still not implemented.

[jakemac53]

ok, I filed a separate bug about the current error that is thrown and linked it here

[eernstg]

FYI: Now sending a CL to review that includes code for upwards-closing the set of reflectable classes in case there is a typeRelationsCapability on the given reflector.