Iterator Helpers: `return` method typing is weaker than ideal

⚙ Compilation target

ESNext

⚙ Library

esnext.iterator.d.ts

Missing / Incorrect Definition

The return method always exists on iterators returned by Iterator.from (iter in below code) and iterators returned by Iterator Helpers methods (iter2 in below code).

However, it is defined as optional in the current definition. This could be improved.

Please note that you can't just add a non-optional return method definition to the IteratorObject type -- iterators returned by builtin methods other than Iterator Helpers don't have that method (iter3).

P.S. if you are interested in a motivating example, I don't have one. Sorry 🤪

Sample Code

const iter = Iterator.from({ next() { return { done: false, value: 0 }} });

iter.return(); // should not error

const iter2 = iter.map(x => x);

iter2.return(); // should not error

const iter3 = [].values();

iter3.return(); // Note: this error IS correct

Playground

Documentation Link

https://tc39.es/proposal-iterator-helpers/

Spec states that below objects always have the return method:

• %WrapForValidIteratorPrototype%
• %IteratorHelperPrototype%

Commencez dans esnext.iterator.d.ts et examinez les définitions de IteratorObject, Iterator.from et Iterator Helpers par rapport au code d’exemple. Vérifiez le comportement attendu à partir de la spécification Iterator Helpers liée : Iterator.from et les résultats des helpers devraient autoriser return(), tandis que [].values() devrait continuer à le refuser. Le travail est terminé lorsque les déclarations distinguent ces cas sans introduire d’erreur pour iter3.