Using async_scope::spawn with a custom allocator

[haggaie]

Hi,

Is it possible to use async_scope::spawn and allocating the operation state using a custom allocator? I tried passing an environment that overrides the get_allocator query but it seems to be ignored.

Looking at the code, it seems that spawn always uses new to allocate the operation state. See here.

Thanks,
Haggai

[dietmarkuehl]

This comment doesn't address the question and only outlines what the plans for a standard scope are:

The description of spawn() in P3149r6 does state that spawn(sender, token, env) would use the allocators associated with env. It isn't particular detailed in how exactly the allocator would be used. The description is a specification, yet. The spawn() in P3149r6 isn't a member function but an algorithm linked to an actual scope via the token.

[haggaie]

Thanks, I noticed that spawn is implemented as a method here and not an algorithm like in P3149r6, but I didn't realize that there are still questions on how allocators would be used.