Should `async_scope::spawn` respect `get_allocator`?

[lixin-wei]

Now in async_scope::spawn, it calls new directly.

I wonder whether it's by design? Can I make it use the allocator in sender's env?

[lixin-wei]

According to https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2025/p3149r11.html#executionspawn, I think it's not by design. It should support custom allocator