Brendan Eich wrote:
>> Does that mean that the host is somehow able to define "===" 
>> semantics for opaque value types (like int64)?  Again, I'm assuming 
>> that int64 is opaque (i.e. not visibly composed of other elements).
>
> It's opaque. If you self-hosted using a Uint32Array of length two 
> (e.g.), you'd have to declare that as the per-instance state for the 
> value class. I didn't show syntax for that -- working on it still. 

And if you for some reason used floats (let's say for complex32, with 
real and imag of float32 type), you'd get the recursive === full glory, 
including NaN !== NaN and -0 === 0.

/be

And if you for some reason used floats (let's say for complex32, with 
real and imag of float32 type), you'd get the recursive === full glory, 
including NaN !== NaN and -0 === 0.