|
|
|
|
|
|
by Gankro
3890 days ago
|
|
|
What have I diluted the meaning of errors to? Rust doesn't remove bounds checks in --release. It's wrapping that gets turned on in release. I'm not sure why you're distinguishing overflow as truly exceptional, as opposed to any other "this should never happen" error? Also I don't think many C libraries that allocate expose that as a failure condition (I've certainly seen some which don't even check!) |
|
|
This is a very common mistake in most C code. Malloc can fail, and it return NULL when it does.