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 almost every method returns a Result even the ones that are infallible internally to stay consistent. A lot of methods actually only return an OutOfMemory error, so panicking on those by default would make it possible to have a slightly better to use api while also sticking to what current Rust does when it encounters OOM situations.
The text was updated successfully, but these errors were encountered:
#17 fixed this in the sense that now all functions that can only return an oom error panic instead. Another change I'd like to see is to figure out what functions may return an oom error and make them panic when they return such an error, ideally allowing us to remove the OutOfMemory variant on the error enum.
Currently almost every method returns a
Result
even the ones that are infallible internally to stay consistent. A lot of methods actually only return anOutOfMemory
error, so panicking on those by default would make it possible to have a slightly better to use api while also sticking to what current Rust does when it encountersOOM
situations.The text was updated successfully, but these errors were encountered: