-
Notifications
You must be signed in to change notification settings - Fork 642
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[1..1000] takes a long time. #857
Comments
It's possible that they are slowing things down. The present implementation Why on earth would you want to write [1..1000] in a strict language though? |
And, to be clear: are you talking about the REPL or compiled code here? The repl takes many orders of magnitude longer on stuff like this. |
Sorry, I was trying out the REPL. Here's my use case:
It shouldn't matter whether it is lazy or strict, as other languages, both lazy and strict handle it fine. I do understand that it presently makes the proofs work well, and that optimization comes later. |
@raichoo just rewrote this to be tail-recursive - it still goes slowly for me, so I imagine that tail recursion isn't a big win in the REPL evaluator. I'm wondering if this is reasonably solvable in a way other than documentation... |
This looks like it is related to Issue #172 |
It looks like using
Nat
s inenumFromTo
is slowing things down. Is there a way to speed this up without losing simplicity and reasonability?The text was updated successfully, but these errors were encountered: