Bradley Farias

> The thing that blocked this proposal last time was “map and set must be treated the same” Kind of, the objection was that Map's argument needs to *reusable* Set's...

@ljharb I do not see it as a valid compromise. It violates the invariant desired that Map is reusable for Set. If we adopt that invariant/feedback the proposal of exclusively...

So, we have to drop the reusability invariant somehow. Dropping Set would accomplish this since there isn't a reuse to make the invariant from. Adding the invariant can be done...

@ljharb Map's argument deals w/ both, so it cannot be exclusively one or the other and be reusable.

I'm not arguing you can't write *something* that works in both, but that is true even if we used a different name for set components like `element`. If you had...

took a quick look at this, the udp/tcp socket factory is causing problems with extensibility, would be much more sane if we could provide a socket/datagram to dump the dns...

It is less about creating a client vs server and more the lack of extensibility. For now sockets are decided for you by the factory in https://github.com/tjfontaine/node-dns/blob/master/lib/pending.js#L46compared to node's ability...

Yes.

@ljharb i think the bind operator changes the general flow and are bigger refactors from normal JS workflows and don't necessarily have the path towards dealing with protocols that this...

@ljharb other bind proposals take an expression and bind the values within that expression. This proposal allows dispatch to match the normal receiver of an expression during invocation using a...