ExE Boss
ExE Boss
There is in the test files.
The benefit is consistency and making it possible to deprecate the non‑`%` form.
@ljharb I’ve rebased this, but some builds didn’t run due to **GitHub** rate‑limiting **Travis CI**.
**ES2018** added the optional `hint` parameter to the [`GetIterator` abstract operation](https://ecma-international.org/ecma-262/9.0/#sec-getiterator), in a backwards incompatible manner.
Actually, `GetIterator(obj, 'async')` can be allowed return an async iterator if `obj` has a `Symbol.asyncIterator` property, and only throw when `CreateAsyncFromSyncIterator` is needed. Also, there’s no way to access `%AsyncFromSyncIteratorPrototype%`...
`CreateAsyncFromSyncIterator` is needed when `obj` doesn’t have a `[Symbol.asyncIterator]()` method.
I think a potentially better option might be to implement a `AsyncFromSyncIterator` helper in a separate package, and then have **ES‑Abstract** depend on it.
I have a work in progress implementation of the **Iterator Helpers** proposal in: [@ExE‑Boss/Iterator‑Helpers](https://github.com/ExE-Boss/Iterator-Helpers).
The current [IsCallable][] spec only tests the presence of `[[Call]]` and not the value of `[[IsClassConstructor]]`: . --- Also, there’s a simpler [IsConstructor][] implementation: ```js const isConstructorMarker = {}; const...
Can please you upload them somewhere so that we can download them while the Maven server is down? (GitHub Releases or Dropbox come to mind, other file sharing services should...