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
When an error happens, the API leaves the user wondering why. I suggest that blosc_compress, blosc2_compress_ctx, blosc_decompress, blosc2_decompress_ctx, blosc_getitem, and blosc2_getitem_ctx should all return -1 on error and set errno. Alternatively, Blosc could define its own error codes with negative values.
This would be especially useful for the decompress routines, which can return an error either because the destination buffer is too small, the data is corrupted, or the decompression library is unavailable.
The text was updated successfully, but these errors were encountered:
When an error happens, the API leaves the user wondering why. I suggest that
blosc_compress
,blosc2_compress_ctx
,blosc_decompress
,blosc2_decompress_ctx
,blosc_getitem
, andblosc2_getitem_ctx
should all return-1
on error and seterrno
. Alternatively, Blosc could define its own error codes with negative values.This would be especially useful for the decompress routines, which can return an error either because the destination buffer is too small, the data is corrupted, or the decompression library is unavailable.
The text was updated successfully, but these errors were encountered: