Date: Fri, 4 Sep 2026 00:21:57 +0300
On Thu, 3 Sept 2026 at 20:12, Rainer Deyke via Std-Proposals
<std-proposals_at_[hidden]> wrote:
> That sounds like a library design issue. If wxWidgets wants to take
> ownership of a pointer, it should take a std::unique_ptr as argument.
Or perhaps wxWidget children should tell their parents to remove said
children when the children
are destroyed, so that you can destroy children first and then the
parents, or in the reverse order,
and both just work.
<std-proposals_at_[hidden]> wrote:
> That sounds like a library design issue. If wxWidgets wants to take
> ownership of a pointer, it should take a std::unique_ptr as argument.
Or perhaps wxWidget children should tell their parents to remove said
children when the children
are destroyed, so that you can destroy children first and then the
parents, or in the reverse order,
and both just work.
Received on 2026-09-03 21:22:19
