kerla
kerla copied to clipboard
Eliminate implicit out-of-memory panics
Currently. Kerla extensively uses containers provided by liballoc. The problem is they can panic on memory allocation failures. Use failable methods (i.e. returning Result<T>) to improve the robustness.
Alternatives to liballoc
- Scapegoat - Ordered set and map data structures
Interested in working on this one, but I can't start now such large assignment.
Great! You don't need to replace all at once. Let's improve the existing implicit panics gradually just like #29.
I took a peek at basic use of alloc in Kerla and what Scapegoat offers and I think it's apples vs. oranges. I remember originally one more crate mentioned, but it's gone now.
I'm afraid replacing Box<T> with something that may gracefully fail is going to be deeply non-trivial as many containers will assume a Box<T> instance can be consumed.