-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add BitOrAssign
etc. to PrimInt
#304
Comments
I think it's because trait MyPrimInt: PrimInt + BitOrAssign + ... {}
impl<T: PrimInt + BitOrAssign + ...> MyPrimInt for T {} |
Don't you gather breaking changes to perform them one day? |
In theory, yes, but in practice I'm afraid that a breaking semver bump will fracture the ecosystem, since these traits are often used in others' public APIs. |
Hm, I guess I'll close this then. |
PrimInt
already has bounds forBitOr
etc. Is it an oversight that the...Assign
variants are missing?Currently, I can do:
...but not:
...when
t
has aPrimInt
bound andcontainer
is initialized withT::zero()
.The text was updated successfully, but these errors were encountered: