Scoped variables: a rough first draft

[Brian Goetz]

Note that there’s naming precedent for this: ClassValue vs ThreadLocal.  

> On Aug 22, 2019, at 9:52 AM, Andrew Haley <aph at redhat.com> wrote:
> 
> On 8/22/19 1:31 PM, Ron Pressler wrote:
> 
>> The general approach is compatible with what we had in mind, except
>> for one important difference: Scope variables must not be
>> mutable.
> 
> OK, so they're really values, not variables, and must be bound to a
> value at binding creation time, so I can lose the set() method,
> 
>> Immutability will allow us to cleanly “inherit” scope variables in
>> multiple strands inside a FiberScope.
> 
> Got it. This might also allow for a cleaner implementation.
> 
> -- 
> Andrew Haley  (he/him)
> Java Platform Lead Engineer
> Red Hat UK Ltd. <https://www.redhat.com>
> https://keybase.io/andrewhaley
> EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671