lcnr
lcnr
From what I can tell this is not expected, `is_const_evaluatable` seems to be incorrect here if `feature(const_evaluatable_checked)` is active. Afaict all of the examples you've given should work without warnings...
@tspiteri this is a bug which only happens with `feature(generic_const_exprs)`, opened #94293 to track that
@peter-kehl this is #94293 again, this lint is only relevant when **not** using `feature(generic_const_exprs)`
@Sycrosity can you provide a complete example where it does not lint?
I would probably continue emitting vtables for ordinary traits which don't have any entries but instead make sure that we never emit any entries for auto traits. cc @compiler-errors @WaffleLapkin
slightly minimized ```rust #![feature(trait_upcasting)] trait Pollable { #[allow(unused)] fn poll(&self) {} } trait FileIo: Pollable + Send { fn read(&self) {} } trait Terminal: Send + FileIo {} struct A;...
Okay, that's very good to know 👍 I thought it only impacted auto traits, moved that concern into a separate issue #131813
not that I can see xd