on implementing state components as a first class concept

[Joe Darcy]

On 4/26/2019 2:28 PM, Brian Goetz wrote:
> 100% on the second.
>
> On the first -- assuming you are speaking _strictly_ of JLM modeling 
> -- that works.  You can call them "class variables", or record 
> components, or whatever.


The working name in the API on the one branch is "state component." For 
the purposes of JLM, I think there should be separate objects for a 
state component as opposed its private instance field representation. 
I'm agnostic on the matter of what the internal compiler representation 
of that information is.

Cheers,

-Joe