[type-annos-observers] Comments on the Nov 7 specification
Michael Ernst
mernst at cs.washington.edu
Tue Nov 20 12:37:16 PST 2012
Eric Bruneton said:
> From an ASM point of view,
> ...
> The important
> point is that all paths should be "from outside to inside" (e.g. for nested
> types, the path should go from outer to inner, not the other way around as
> proposed in the Nov 7 specification).
Eric, I'm willing to make this change, but I would like to be able to give
a more specific justification for the design choice. Can you explain the
rationale, or what difference it makes to ASM? Is the reason that the
identifiers appear left-to-right in the class file and you want to process
them in that order, or is it something else?
(The current numbering was starting at what I think of as the real or main
type, and then adding auxiliary information afterward, just as it does for
generics. So "outside to inside" might need some more explanation in the
documentation.)
Thanks!
-Mike
More information about the type-annotations-spec-experts
mailing list