Kevin Gibbons
Kevin Gibbons
I'm fine with this approach, then.
Previously discussed in https://github.com/tc39/ecma262/pull/1288.
My preference is to move the check and thrown error out of `AddEntriesFromIterable` and into the two callsites (Map and WeakMap) which need it, and leave the type for `AddEntriesFromIterable`...
Pushed up a commit with the change I suggested in the previous comment, now LGTM.
This actually isn't quite the same thing that [#2236](https://github.com/tc39/ecma262/issues/2236) is talking about - the example you've put here is about the observable behavior of algorithms, not the way we write...
> factor out FindViaPredicate (say) [...] push those non-common steps back to the caller functions. Per editor call we like that option. Also there is a `Get` in the loop...
Yeah I'll need to update ecmarkup. Which unfortunately is going to either mean a backport (ugh) or landing https://github.com/tc39/ecma262/pull/2901 first after all and rebasing this. We'll talk about it at...
>is there an official definition for is-a relation in the JavaScript spec? No. > what about subtyping in the general OOP sense? No. > should one be added? In my...
Per editor call today, now that we have an [auto-formatter](https://github.com/tc39/ecmarkup#formatter), we'll have the formatter translate from HTML entity style (which some people prefer to write) to actual code points (which...
You can Function.prototype.toString.call both a Proxy for a function and `document.all` (and a Proxy for `document.all`, for that matter).