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
I'm responding to all -1s by exponentially increasing my buffer size until I hit 2GB-1, at which point I assume continued failure means the data is corrupt, but it would be nice to differentiate these cases via the return value.
The text was updated successfully, but these errors were encountered:
Cool, I was kind of imagining that this would be considered a "breaking change" and not really feasible, but I if there were explicitly no guarantees about return codes previously, other than e.g. "negative means error", then it's not a big deal?
Would the process basically be to replace every return -1 with a unique integer, and document it?
While decompressing via JBlosc, I was hitting a
-1
return value from because my "dest" buffer wasn't big enough.I'm responding to all
-1
s by exponentially increasing my buffer size until I hit 2GB-1, at which point I assume continued failure means the data is corrupt, but it would be nice to differentiate these cases via the return value.The text was updated successfully, but these errors were encountered: