Thanks for the nits, cuz this kind of thing is all about nits! Agree with the first two, re your third one, it’s safeSub and safeAdd that would protect from overflows. Like the transaction, they’re more complex in the sense that their implementation is probably slower and more code, but simpler in the sense that they have a less constrained “safe space of operation”. (I am in search of a better term for that.)
Thanks for the nits, cuz this kind of thing is all about nits! Agree with the first two, re your third one, it’s safeSub and safeAdd that would protect from overflows. Like the transaction, they’re more complex in the sense that their implementation is probably slower and more code, but simpler in the sense that they have a less constrained “safe space of operation”. (I am in search of a better term for that.)