> it also means sugar like Rust's for loop, which de-sugars into trait invocations, can never be constant today.

Yep, that was my annoyance.

Const allocation is possible in Rust as an unstable feature. Not sure if you can persist it to runtime, though you can persist a reference which will become a static reference. I think it being unstable is why I needed `include_bytes!`.