Re: Unordered setsmaps, for when ordering is hard/expensive/unwanted?

Consulting with bz and dbaron, it sounds like you're right: 
implementations won't be able to swallow the "as if self-hosted" 
overhead that's required to keep canonical "insertion" order preserved 
for later reflection.

Bjoern still makes a good point. Studying Go as you suggest could help, 
but I think only in discovering "true positive" results ("positive" in 
disease-testing sense). If all seems well, that is unfortunately not 
enough assurance.

(Data races that I'm concerned about are among JS-programmable threads, 
so workers -- not network.)

/be

Received on Monday, 2 September 2013 17:33:15 UTC