domenic at domenicdenicola.com (2014-01-22T20:41:42.357Z)
Makes sense, but I thought the user could not define semantics for "===":
it just means "===" for each of its data members ("structural recursive
strict equality test").
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).
[oops - reply all this time] > Value objects have value, not reference, semantics. JS has string number > boolean already (note lowercase names). With value objects, users and the > host env can define others. > Makes sense, but I thought the user could not define semantics for "===": it just means "===" for each of its data members ("structural recursive strict equality test"). 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). -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140116/04b607f6/attachment.html>