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
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.
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.
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
The text was updated successfully, but these errors were encountered: