tc39 / proposal-iterator-unique

a proposal to add a method to iterators to produce an iterator of only its unique values

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Align/merge with Array.unique proposal?

Jack-Works opened this issue · comments

Align how? Also, I don't think I would want to merge because I'm not very interested in championing any array methods. See related discussion in tc39/proposal-joint-iteration#1.

Align how?

On naming and API design.

Generally speaking, proposals like this advance independently, and whichever comes second follows the design of the first (insofar as the principle which informed that design carry over).

I'd like to follow the API design of this proposal if you find the design has some flaws, but I hope the naming can follow Array.unique because it's more risky to choose a name on Array (if the author @TechQuery still want to push Array.unique forward)

(if the author @TechQuery still want to push Array.unique forward)

@Jack-Works I'm so sorry for the delay of my proposal.

In the latest years, I am so busy at making my startup company survived during COVID-19. I have few time to learn how to write a formal specification document.

As my company becomes working well & ES decorator stage-3 has been shipped in all of my open source projects , I finally have enough time to finish this proposal this year.

Except lack of specification document, I am using my proposal API polyfill in many projects, such as kaiyuanshe/kaiyuanshe.github.io#297 (comment) few days ago.