Looks like this version of lazy-list and even lazy itself have been depreciated, thus my PR is closed.
I also looks like the recommended non-memoizing version of lazy-list has the same memory leaks for very long (infinite) lists, and thus needs my PR applied to it. The rational to depreciating these seems to be performance when applied to their limited use in tests and I see that, as I tried to make changes to Lazy that would improve its lack of performance when run on some JavaScript engines that handle internal functions calling functions very poorly. However, I strongly disagree with removing these memoization versions of the libraries from the language, as just because they aren't needed for tests doesn't mean they are never needed. Noah has suggested that one can implement memoization themselves when needed, but hasn't explained how one can do that and remain referentially transparent and not use JavaScript without using Lazy, and if one does implement Lazy themselves, then the resulting code won't be accepted for libraries because it contains JavaScript. This thread is probably not the place to discuss this, although it is going to affect the objective of the OP, but I don't know where it should be discussed since Noah has requested we don't discuss it on elm-dev. I'll cease and desist about this if someone can show me how to write referentially transparent deferred memoization of the result of a function call without using Lazy or JavaScript. On Nov 14, 2017 17:20, "'Rupert Smith' via Elm Discuss" < [email protected]> wrote: > On Monday, November 13, 2017 at 11:48:19 PM UTC, GordonBGood wrote: >> >> The LazyList library as it exists is seriously flawed as it crashes for >> many cases for infinite length lazy lists, which is probably why there is >> that caution. Please see my extensive PR which fixes almost every function >> so they can handle infinite length lazy lists within the guidelines. > > > That is not so good, as infinite lists is much of the point of lazy lists. > Lets ping the package maintainer and find out why your PR is just sitting > there since February. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Elm Discuss" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/elm-discuss/BM_ZmUk-vck/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
