That proposal wasn't about ranges, even though it might look like it was. It's about a special type of numeric array conversion that's really about a particular sequence that isn't all that special in the context of programming. [1] It also links to an SO question that almost reads like a homework/"gimme teh codez" question. [2]
[1]: https://oeis.org/A217626 [2]: https://stackoverflow.com/q/54433007/2693146 ----- Isiah Meadows cont...@isiahmeadows.com www.isiahmeadows.com On Thu, Mar 7, 2019 at 6:28 PM Bob Myers <r...@gol.com> wrote: > > There is already a very well thought out list, although to my knowledge it > has never been officially blessed, at https://esdiscuss.org/topic/ranges. > > Quoting: > > It seems odd that after all these years of discussions and meta-discussions > about ES feature proposals, some people are still saying things like: > > there really needs to be > I'd really like > I'd love to have > > often without addressing a single one of the relevant questions: > > Is it sugar? Is it "mere" syntactic sugar (which is not disqualifying in and > of itself), or something that requires (or benefits from) being baked into > the language? > How much sugar? If it is wholly or partially syntactic sugar, what the degree > of syntactic optimization? > Frequency of benefit? What is the frequency of the use case? > Expected improvement? If it is something that would benefit from being baked > into the language, what is the degree of the benefit (eg, in terms of > performance)? > Userland implementable? Can it be implemented in userland code? If so, what's > the downside of that? > Implementable? Does it present potentially difficult or intractable > implementation challenges? > Consistent? Is it consistent with existing syntactic and semantic practices > in the languages? > Holistic? Does it fill in some obvious logical gap in the current language > design? > Understandable? Does it place an unsustainable new "cognitive burden" on > learners and users of the language? > Library? Is is something that would be better provided as part of some kind > of future standard library? > Intrusive? Does it take over real estate that might be useful for future > features no one has thought of yet, the obvious example being using special > characters? > Readability? Is it something that results in a distinct improvement in > readability or visible semantic correctness of code? > Prior art? Has this or a similar feature already been proposed, and if so > what was the reaction, and how is your proposal different from that, or from > a similar features existing in other languages? > > I'm sure there are cases where simply throwing out an informal idea and > seeing how people react is useful to get a discussions started, but most > reactions will be that the proposal does not meet one or more of the above > criteria, so proposers could save themselves and other people lots of time in > advance by explaining HOW their proposal satisfies these points, not all of > which are relevant to every proposal, but those which are. > > Bob >>> >>> It would be useful to have a FAQ somewhere with a version of the above 4 >>> rules that is better worked out and justified, so we could point to that. >>> (From whatever public-facing forum is selected for the future; this one is >>> dead.) > > _______________________________________________ > es-discuss mailing list > es-discuss@mozilla.org > https://mail.mozilla.org/listinfo/es-discuss _______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
