Kevin Gibbons

@pitaj Let's keep the general discussion of the utility of `return` to #30, and leave this issue specifically for talking about the analogy to `yield`.

Re: calling convention, we could have `Functor.map` be a function object which just invokes the symbol-named method on its first argument, and also give the function object a `Symbol.toPrimitive` method...

Ditto unnecessary emu-xrefs https://github.com/tc39/ecma262/pull/3196

The history of these proposals is more complicated than any other since the adoption of the current process, as far as I'm aware, and the merger in particular was not...

I'm aware; see the section on "possible vs practical".

I'm curious which libraries are doing this, if you'd be OK naming them. On rare occasions I've encountered pages where some code was e.g. pulling XHR out of an iframe...

Interesting, thanks! I'm very surprised to see an analytics company in there; I've seen a _lot_ of analytics code, and while it's quite common for such code to be virtualizing...

Yes, I know. My point is that there is a lot of code which relies on this capability _not_ being available to userland. (Or rather, to be precise, being available...

Service workers don't really compose, can't generally be provided as part of a library, and only even see requests to the same origin, so they are not a solution to...

> Sure though to be fair proxying requests only worked for XHR/fetch Yes, but it does work for those. And that capability is very widely relied upon. > Would love...