Infeasible
Status Update
No update yet.
Comments
en...@google.com
da...@google.com
ma...@google.com
We are aware, but as you said there is nothing we can really do now. I agree it's a weird inconsistency, we'll look at our review processes around this, but there is nothing actionable I can really do to address it.
ma...@gmail.com
Perhaps the only thing you can do is modify (u)ints instead of status_t, and maybe even add some (doc)comments. That should prevent some future confusion and hopefully not lead to someone returning the "correct" negative status_t constants in some new API or codepath in the future (either intentional or by forwarding an API that already returns negative error codes).
Thanks either way!
Description
The
AThermalbindings describe that most functions returnintwith positive error codes.However,
status_tvalues. All validstatus_tvalues areSurfaceTexture,HardwareBuffer,NativeWindow,InputQueue) are expected to return negative error codes.I guess we can't expect this to change, as the API is already public and the documentation doesn't state the expected return values are negative. Just letting you know that this is an unnecessary inconsistency once again.