The bug is that `x % 255` is not quite the same thing as `x % 256`; but `x & 255` is. The stylistic issue is that `numeric_limits<uint8_t>::max()` is a very verbose way of spelling `255`.pull/536/head
parent
f8b883dcd4
commit
9504d804e0
Loading…
Reference in new issue