On Tuesday, 12 March 2019 16:06:59 UTC+1, Matthias Felleisen wrote: > > > > > On Mar 12, 2019, at 10:48 AM, bedeke <bed...@hotmail.com <javascript:>> > wrote: > > > > > > Sorry for not being clear. > > I knew that increasing the memory limit could make this run without > problems since the data in each cell of the stream is so small. > > I was running this example with a memory limit of 128MB. > > I made my own quick stream implementation, and this runs the above > example with the low memory limit without problems and without noticeable > GC happening. At the cost of having to reevaluate every stream from the > beginning. > > I was just curious if there was a stream implementation that avoids > memoization. > > > The very notion of ‘stream’ implies memoization. What I am surprised about > is that racket/stream (unlike #lang lazy) does not memoize exceptions, > which is even more expensive — Matthias > > Ok,
thank you. Then I will search in a different direction. I wanted to avoid generators, but it looks like this will be the better option. B. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
