Improving the format of type annotation attributes
dl at cs.oswego.edu
Thu Sep 13 13:12:15 PDT 2012
On 09/13/12 15:31, Alex Buckley wrote:
> Then we must make a choice. The low-risk approach is simply to move the location
> information earlier in the type_annotation structure. The high-risk approach is
> to drop the "counted" approach to location information and adopt the "nested"
> location approach.
Where "risk" amounts to throwing away and redoing part of the
current reference implementation that encodes and decodes annotations?
I'm not sure that anyone not involved in encoding/decoding (not me)
can give much guidance, but offhand, the nested approach looks
more amenable to addressing some of the comments posted by Eric Bruneton?
More information about the type-annotations-spec-experts