Now I'm wondering if lazy lists might not be the answer. I need the top weighted actor for a role, but sometimes I need the second top one, if the top one fails further tests along down the road. Or the third top, etc, sounds like a lazy list to me. My weird db ideas are structured like lazy lists anyway. I probably throw a bunch of lazy/force/delay constructs in there, and it's suddenly intuitive, functional, and simple and then I go yell at the Haskell devs to fix their language so it isn't unpacking 900 megabytes just to compile stuff on someone's computer. (to compare, glibc/gcc is like 130 megabytes, plus the 15 or so for chicken)
_______________________________________________ Chicken-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-users
