To make the diagram easier to use, I have added a legend
that explains its various notations.
On Mar 13, 2019, at 8:44 PM, John Rose wrote:
>
> In the following explanations you may with to consult this diagram of
> constant pool relations, which is derived from my current draft:
>
> http://cr.
Yes from me to all your points here.
A conditional child segment doesn’t need any new holes, just there BSM based
predicate you mention. This works equally well for conditional fields, methods,
and nested types.
Conditional supers seem to require some special pleading with DefaultType to
car
>
> (What's an optional member of a template? Ah, that's a good
> conversation. I haven't written this one up yet. I think the cleanest
> way to formulate those is in terms of *optional child segments*.
> I can think of many different ways to gate their optionality,
> and BSM-based instantiatio
