Sets plus JSON

Nicholas C. Zakas standards at
Thu Oct 4 11:02:45 PDT 2012

On 10/3/2012 4:44 PM, Allen Wirfs-Brock wrote:
> (oops, forgot to reply-all)
> Begin forwarded message:
>> *From: *Allen Wirfs-Brock <allen at 
>> <mailto:allen at>>
>> *Date: *October 3, 2012 10:15:57 AM PDT
>> *To: *Herby Vojc(ík <herby at <mailto:herby at>>
>> *Subject: **Re: Sets plus JSON*
>> This is one of the reasons that it is important that Set (and Map, 
>> etc.) are specified (and implemented) in a manner that makes them 
>> fully subclassable.   By subclassing, individual use cases for 
>> serializing them can be kept distinct rather than multiple libraries 
>> or subsystems fighting over who gets control of the single 
>> implementation of Set.prototype.toJSON
That doesn't necessarily preclude a logical default, correct?


Nicholas C. Zakas

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the es-discuss mailing list