LWG issue 4356 talks about adding allocator customisation for connect-awaitable but should ensure that the allocation is freed before the resulting operation completes to ensure that the memory resource can be freed upon completion.
We should also consider having blanket wording in the get_allocator query that limits the scope of use of the returned allocator similarly to get_stop_token.
There is a question about whether or not this should be done by the callee before invoking the completion-function, or by the caller by destroying the operation state before releasing the resources.
LWG issue 4356 talks about adding allocator customisation for connect-awaitable but should ensure that the allocation is freed before the resulting operation completes to ensure that the memory resource can be freed upon completion.
We should also consider having blanket wording in the
get_allocatorquery that limits the scope of use of the returned allocator similarly toget_stop_token.There is a question about whether or not this should be done by the callee before invoking the completion-function, or by the caller by destroying the operation state before releasing the resources.