isiahmeadows at gmail.com
Thu Jul 19 09:13:23 UTC 2018
I'd rather keep it restricted to very simple, context-free things like a
reverse subtract or single add, with only a few bits of data necessary.
Anything more is going to be a perf concern because you can't avoid visible
On Thu, Jul 19, 2018, 05:03 Michael Luder-Rosefield <rosyatrandom at gmail.com>
> This array view thing is very close to what I had in mind, and seems to
> suggest to a lot of interesting possibilities.
> What strikes me as the two most significant are:
> - again, 'reversed' is just one alternative iteration order through,
> though almost certainly the most useful
> - others I can think of could be 'even/odd indexes', 'random shuffle',
> 'iterate-until /while-condition', and filter equivalents
> - as well as the view defining the iteration order, it could define
> the computed value
> - this would be basically a map where the value isn't computed
> until accessed; caching behaviour could be user-determined
> On Thu, 19 Jul 2018 at 09:49 Isiah Meadows <isiahmeadows at gmail.com> wrote:
>> What about this alternate proposal:
>> (I've got a myriad of other related stuff there, too.)
>> On Thu, Jul 19, 2018, 04:41 Dmitry Shulgin <shulhindvst at gmail.com> wrote:
>>> Above we was talking about this.
>>> consistency and handy using -- two main reasons for this proposal.
>>> `reverse` will also mutate my array, cause of in-place implementation.
>>> You can find workaround for many existing methods, but it's not handy to
>>> my mind.
>> es-discuss mailing list
>> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss