Tracking issue for unsizing casts in const fns

[oli-obk]

Right now we don't allow unsizing casts (array -> slice or type -> dyn Trait) in const fns on stable.

While we can't allow unsizing to dyn Trait until we've figured out trait bounds in const fns, we can easily allow unsizing casts for slices, there's no reason not to have them. The only reason we didn't have them in the initial min_const_fn feature gate was the fact that we preferred overly aggressive rules over accidental stabilization.

The relevant code is

rust/src/librustc_mir/transform/qualify_min_const_fn.rs

Lines 162 to 165 in dc45735

	Rvalue::Cast(CastKind::Pointer(PointerCast::Unsize), _, _) => Err((
	span,
	"unsizing casts are not allowed in const fn".into(),
	)),

We need to check the destination and source types for slice and array respectively and permit the cast in that case. We also need to recurse with check_operand on the value that is being casted.

[RalfJung]

Judging from the feature message, nowadays slices seem to be allowed by dyn unsizing is still disallowed -- but only in const fn. We also have no tests using this feature (just some compile-fail tests checking the feature gate).

I am not entirely sure why these casts are disallowed only in const fn, but I assume it is a matter of backwards compatibility. However, this means we already have to be sure that the corresponding Miri code is right, so -- what is blocking us from simply removing this feature gate, and allowing the corresponding code?

[RalfJung]

In fact while trying to write a gate test for #84310, I was unable to find any example of a piece of code that compiles once const_fn_unsize is allowed. I always then additionally get the error about "trait bounds other than Sized".

@oli-obk If we just removed this UnsizingCast in check_consts/ops.rs and all its call sites, is there any additional code that would be accepted?

[RalfJung]

Ah I found something

const fn test() {
    let _x = NonNull::<[i32; 0]>::dangling() as NonNull<[i32]>;
}

I am not sure why this is gated. It's not a slice directly, but it's also not a lot more complicated.

[oli-obk]

Slices are OK, trait objects aren't. If the same code snippet but with trait objects fails even with the feature gate, just removing that check is fine by me (needs stab report and lang team approval on the stab PR)

[RalfJung]

Yeah, there is a rather aggressive check for dyn Trait appearing anywhere that triggers "trait bounds other than Sized are unstable".