EG meeting *canceled*, 2022-08-24

[Dan Smith]

No EG meeting today.

There were a few followup emails to last meeting's discussion about terms like "object" and "instance", but I think we've covered that topic pretty well and there's not much more to say.

We might benefit from further discussion of the other topics I listed last week, but what I think would be best is if there are open questions or ideas to pursue, post something in the thread, and we'll touch on it next time.

For reference, here was the list from last meeting:

> Lots of recent threads that could be further discussed:
> 
> - "Question about universal type variables": Kevin started a discussion about how type variable types should be modeled, and what changes when they become universal
> 
> - "Updated SoV, take 3": Brian revised the State of Valhalla document to reflect recent design ideas
> 
> - "object sameness, Lebniz's Law, ...": John elaborated on SoV review comments regarding value object equality/substitutability
> 
> - "The storage hint model": Remi shared thoughts about using a storage attribute, rather than a value type, to encode flatness
> 
> - "The problem with encapsulating C.val + autoboxing": Remi discussed the treatment of access-restricted value types in generics
> 
> - "where are all the objects?": John and Kevin discussed usages of the terms "object" and "instance"
> 
> - "one class, two types, many bikesheds": John discussed how we model classes vs. types, the relationship of ref and val types, and how syntax like .ref and .val might be used
> 
> - "Value type companions, encapsulated": John shared a document describing how access restrictions could be enforced on value types
> 
> - "races on flat values": John discussed how the memory model needs to be updated to describe concurrent accesses of flat variables