We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is a breaking change, but one in line with how the language has evolved.
{ilog, ilog2, ilog10} should all be methods in PrimInt. These have been stable for almost 2 years.
{ilog, ilog2, ilog10}
Also probably the checked variants, too.
The signatures are essentially
pub const fn ilog(self) -> u32; pub const fn ilog2(self) -> u32; pub const fn ilog10(self) -> u32;
EDIT: as a stopgap, these could go in a ILog trait and just be there for use to avoid breaking everything.
ILog
The text was updated successfully, but these errors were encountered:
They can go on PrimInt if you can figure out generic default implementations.
PrimInt
Sorry, something went wrong.
No branches or pull requests
This is a breaking change, but one in line with how the language has evolved.
{ilog, ilog2, ilog10}
should all be methods in PrimInt. These have been stable for almost 2 years.Also probably the checked variants, too.
The signatures are essentially
EDIT: as a stopgap, these could go in a
ILog
trait and just be there for use to avoid breaking everything.The text was updated successfully, but these errors were encountered: