Ensure stack overflows don't kill Ludus #27
Labels
No Label
accepted
bug
clj
documentation
enhancement
errors
infrastructure
later
next
now
optimization
proposal
question
research
semantics
syntax
ux
vm
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: twc/ludus#27
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I don't know if this is actually an issue, but test it and ensure it's not:
ludus-web
environment#29 helps but does not fix this. If recursive calls are in tail position, we won't get stack overflows. But beginners may overflow the stack by non-tail recursive calls, and we don't want that to crash ludus-web.
At current, a stack overflow will cause a wasm out of memory issue; not sure how to recover that.
Meanwhile, an infinite loop will also hang.
Neither of these are recoverable, but hitting reload now automagically puts your code back in the browser, so you won't lose work.
Bumping to next milestone.
This will be possible with the new actor model.