Add carry/borrow to Fallible<MutableDataInt.Body> #148
Labels
addition
oh, so shiny!
brrr
such code, much wow
maybe
to do, or not to do?
subtraction
huh? where did it go?
The
MutableDataInt<Element>.Body
model has many operation pairs similar to this:The
*SubSequence
operations represent some core algorithm that stops at the end of the given arguments. The non-*SubSequence
carries or borrows the error indicator after that point. What if I instead add acarry()
andborrow()
toFallible<MutableDataInt.Body>
? I believe those two methods would make every non-*SubSequence
variant obsolete.The text was updated successfully, but these errors were encountered: