Should heap and stack exhaustion be catchable?
Open
enhancement
high reward
medium effort
user experience
- Dominant language
- Standard ML
- Stars
- 1.2k
- Forks
- 104
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 16
Description
Right now we always abort, but I think the system is in a state where raising a ML exception is possible.
This would be particularly useful for a future REPL.
There are semantic issues here if we want to allow optimizations that reorder two writes to mutable objects with an allocation point between them.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.