Rob Browning <[EMAIL PROTECTED]> writes:
>
> The implementation works (it passes all of the tests they provide),
> and I believe could completely replace Guile's existing eval.c
> force/delay, but I wanted to know if anyone knew of a reason it
> shouldn't.

I remember I thought it could go in C in the core nicely enough, or at
least just extending `force' in the core and leaving the actual
`eager' to the srfi module perhaps.  I don't remember the details
though, except it might be nice to lose the mutexes at the same time
:), for speed and size.

http://lists.gnu.org/archive/html/guile-devel/2005-12/msg00050.html


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel

Reply via email to