This traitshould theoretically be a supertrait ofPrimInt. However, this trait (likeNumOps: Rem), requiresCheckedRem.PrimInt does not currently require that, meaning that this would be abreaking change. (PrimInt: CheckedNumOps for a future release?)

I think it's just thatCheckedRem didn't exist at the time. Yes, it would make sense, but also yes, it would be a breaking change.

You did not actually includeCheckedNumOps: CheckedRem though -- did you mean to?

I wrote all that out about it and forgot to actually requireCheckedRem. I think my idea was that I'm not sure what should happen with it.CheckedNumOps couldnot requireCheckedRem and be a supertrait ofPrimInt, or itcould requireCheckedRem and be disconnected fromPrimInt. I wasn't sure on the best course of action, so I think that's why I leftCheckedRem out.
However, now I think that usingCheckedRem is the right way to go. If you don't think so you can roll back the most recent commit to the fork, which actually addsCheckedRem.