You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for sharing Hackett. It seems to bring out the best of haskell and scheme.
Just want to check if there is any way to turn off lazy evaluation. I noticed that lazy evaluation is more of a hindrance after the prototype stage (from my Haskell experience).
If I want to patch Hackett to use strict evaluation for my purposes, Is that a big effort?
Thanks again
The text was updated successfully, but these errors were encountered:
I noticed that lazy evaluation is more of a hindrance after the prototype stage (from my Haskell experience).
This seems like an odd statement to me. Perhaps you could elaborate on it?
That said, I have not decided on a default evaluation model for Hackett. I’d like to make laziness work, but it would be a significant undertaking. In the short term, I’m not sure what my plan is going to be, but in the long-term, I think it would definitely make sense to have a #lang hackett/strict and/or a #lang hackett/lazy to complement the default evaluation model.
Hello,
Thanks for sharing Hackett. It seems to bring out the best of haskell and scheme.
Just want to check if there is any way to turn off lazy evaluation. I noticed that lazy evaluation is more of a hindrance after the prototype stage (from my Haskell experience).
If I want to patch Hackett to use strict evaluation for my purposes, Is that a big effort?
Thanks again
The text was updated successfully, but these errors were encountered: