1.92 regression: overflow evaluating MetaSized

[Mark-Simulacrum]

[INFO] [stdout] error[E0275]: overflow evaluating the requirement `ElementArray: MetaSized`
[INFO] [stdout]    --> hwc_lang_cbml/src/tags/src/parse/mod.rs:3:48
[INFO] [stdout]     |
[INFO] [stdout]   3 | pub fn parse_file_tokens(tokens : &[Token]) -> Result<File, String> {
[INFO] [stdout]     |                                                ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] note: required for `Box<ElementArray>` to implement `ParseTokens`
[INFO] [stdout]    --> hwc_lang_cbml/src/tags/src/parse/combinators.rs:5:32
[INFO] [stdout]     |
[INFO] [stdout]   5 | impl<T : ParseTokens + ?Sized> ParseTokens for Box<T> {
[INFO] [stdout]     |      -                         ^^^^^^^^^^^     ^^^^^^
[INFO] [stdout]     |      |
[INFO] [stdout]     |      unsatisfied trait bound introduced here

(https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/red-lightning123.hwc/log.txt)

This might be a duplicate of #143830 but unless we reverted and re-landed something I assume there's a separate breaking change that caused this, which may need its own FCP. Filing this so we can figure that out.

[zachs18]

repo: https://github.com/red-lightning123/hwc

searched nightlies: from nightly-2025-08-02 to nightly-2025-11-16
regressed nightly: nightly-2025-10-16
searched commit range: 844264a...57ef8d6
regressed commit: 57ef8d6

bisected with cargo-bisect-rustc v0.6.11

Host triple: x86_64-unknown-linux-gnu
Reproduce with:

cargo bisect-rustc --preserve --start=1.90.0 

I think this the same as the known error for the old solver tested by https://github.com/rust-lang/rust/blob/main/tests/ui/sized-hierarchy/overflow.rs which is mentioned in the PR description for the regressing PR #144064

[jieyouxu]

cc @davidtwco (in case this is unexpected)

[davidtwco]

Closing as duplicate of #143830, this is the same regression that we knew about and did a t-types FCP about, we just fixed it and un-fixed it when we skipped MetaSized goal temporarily and then landed a proper fix.