-
Notifications
You must be signed in to change notification settings - Fork 215
Use of mp_ilogb in mp_radix_size #366
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
Conversation
|
Btw, why are we having ilog and not ilog_u32 like for expt. Furthermore why ilogb and not ilog, I mean it is integer logarithm and not logbrithm. Sorry for the off topic comment. |
|
Hmm, I am unsure about this one. In general I like it but I am a bit hesitant of adding it to 1.2, since we are delaying the radix overhaul to 2.0 |
|
Ping @sjaeckel |
bd2a4db to
c06b4c2
Compare
It is integer logarithm for different integer bases.
Seems to sound better, yes, so if you want that: I can do that, no problem. Now that you mention it: didn't we have a discussion about that or was it only about |
|
Ok, I didn't know ilogb was also in the c11 standard. I've read in the docs that the b refers to base, but this only makes sense if there are other functions with a fixed base like log and lg. We also don't have exptb, right? But given the C name I am ok with your choice. |
|
I'm also pro |
|
Hmm, I've lost track on what is realeased and what not. If we can still change the names I would prefer mp_log and mp_exp (maybe with _u32 suffix if desired). No b suffix for both since both have a base specified and we don't provide specialised functions with fixed base. Maybe also call it ilog, but I think it is already obvious that we are talking about an integer logarithm Here. I think c had to use the weird name due to all the many c log functions already existing. |
fine by me to change it to Edit considering the existence of |
|
So it's |
34ef151 to
7ca5e1f
Compare
0c748e3 to
3cb2509
Compare
3cb2509 to
80f5818
Compare
PR slicing as asked for in #343