The next EG Zoom meeting is tomorrow, 4pm UTC (9am PDT, 12pm EDT).
The only active topic in the mailing list is "Revisiting default values". We
discussed it last time, and I'm not sure there's much new to add to the
discussion right now. (I'm pursuing some internal explorations, not ready to
> On Jul 28, 2020, at 11:33 AM, Tobi Ajila wrote:
>
> > Bucket #3 classes must be reference-default, and fields/arrays of their
> > inline type are illegal outside of the declaring class. The declaring class
> > can provide a flat array factory if it wants to. (A new idea from Tobi,
> > he'll
I think it would help if we had a clear sense as to what proportion of
inline-types we think will have this "bad default" problem. Last year
when we discussed null-default inline types the thinking was that
about 75% of the motivation for null-defaults was migrating VBC, 20%
for security, 5%
> Bucket #3 classes must be reference-default, and fields/arrays of their
inline type are illegal outside of the declaring class. The declaring class
can provide a flat array factory if it wants to. (A new idea from Tobi,
he'll write it up for the thread.)
```
public sealed abstract class
