|
|
|
|
|
by Manishearth
3687 days ago
|
|
> Try using Rust without boxing, for example, as is necessary if you want to catch OOM. It's not necessary, you can plug in a custom allocator that works differently and use boxing as usual. There are plans for more robust custom allocator APIs that make this even easier to handle. Also, really, even if Rust didn't have this, the situation wouldn't be worse than C. In C you have to malloc and free things manually. In Rust you can do that too. Rust's abort-on-OOM is an stdlib thing (which can be overridden as previously mentioned). |
|