Is there a timeline for aligning the abilities of
const fn so that these are not covered by two different checks (const_qualif vs min_const) any more?
not that I know of. Note that
const fn is
const_qualif + min_const, so essentially the work is to eliminate
min_const contains another intrinsic whitelist and I am not sure why that is there (as opposed to in
do we not want to allow the same intrinsics in stable
const fn and
@RalfJ It does seems like we should -- so the whitelist should be moved?
or just used in
(latter is my preference)
hm I may have misunderstood what that file is even about
the main difference between stable
const fn AFAIK is access to union fields, but that check is in
qualify_consts. all the stuff in min_const should apply to everything on stable, not just functions.
@RalfJ FP math as well iirc
casts to function pointers and trait objects
I feel I should know this by heart but I have amnesia about stable
@Matthew Jasper :face_palm:
the cast and arithmetic checks are in
but they are also duplicated in
qualify_consts for promotion^^