constify vec![1, 2, 3] macro

[Lars-Schumann]

Tracking issues:
const_heap: #79597

makes all the parts needed for non-empty vec![] macros const:

alloc::boxed::box_assume_init_into_vec_unsafe
alloc::boxed::Box::assume_init
alloc::boxed::Box::into_raw_with_allocator
alloc::boxed::Box::new_uninit
alloc::slice::[T]::into_vec

Note that this does not allow for the use of the vec![(); 4] arm of this macro to be used in const-eval, since that uses specialization (spec and const traits don't really like each other so I didn't want to touch any of that in this).

[rustbot]

r? @TaKO8Ki

rustbot has assigned @TaKO8Ki.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

• Owners of files modified in this PR: compiler
• compiler expanded to 75 candidates
• Random selection from 21 candidates

[rustbot]

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

[Lars-Schumann]

r? @rust-lang/wg-const-eval

[lcnr]

r? wg-const-eval

[oli-obk]

Keep using the vec macro and just fix up the diagnostics. Can even enable the feature

View changes since the review

[Lars-Schumann]

Ok, many of these have no more errors now since a Vec of ZSTs doesn't allocate.
If we would rather keep these failure cases, I can make MyOwned non-ZST, or introduce cases with a separate non-ZST type.

[rustbot]

Reminder, once the PR becomes ready for a review, use @rustbot ready.

[Lars-Schumann]

@rustbot ready