Check type selection for sizes about libde265 HOT 4 CLOSED

No, that just hides errors and there is no reason to save this one bit. If some computation gives negative values, errors are obvious. If you use unsigned, they overflow and are more difficult to find.

from libde265.

I am surprised that you do not like unsigned integers here. I would prefer their use at various places to make the software a bit safer by design.

from libde265.

Feel free to do so.
And then have fun with code like

for (uint32_t i=length-1;i>=0;i--) { ... }

2013/9/6 Markus Elfring [email protected]

I am surprised that you do not like unsigned integers here. I would prefer
their use at various places to make the software a bit safer by design.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-23928788
.

from libde265.

for (uint32_t i = length - 1; i >= 0; --i) { ... }

Would you like to point out that the data types "uint32_t" and "size_t" have got different value ranges eventually?

from libde265.