2 ms·
Lots of things that must be memory-safe are run on top of the Linux kernel, which doesn't give you the OOM-safety you're looking for because of overcommit+OOM k
by littlestymaar 6y ago
Lots of things that must be memory-safe are run on top of the Linux kernel, which doesn't give you the OOM-safety you're looking for because of overcommit+OOM killer.
Anyway, for Windows and other plateform where this is a reasonable goal, there is work in progress to add this to Rust. See this RFC[1] which has been merged and whose implementation progress can be followed here [2]
[1] https://github.com/rust-lang/rfcs/pull/2116 https://github.com/rust-lang/rfcs/pull/2116
[2] https://github.com/rust-lang/rust/issues/48043 https://github.com/rust-lang/rust/issues/48043
- jorangreef 6y agoLots of things are done that way but there is also plenty of software for which OOM safety is a critical component of memory safety. As you say, not every platform is Linux, and if Rust will be moving towards OOM safety as a global default and making this explicit throughout the std lib, then I think we are both in agreement.