Re: delayed_forward: good, bad, ugly?

From: Hans Dembinski (hans.dembinski_at_[hidden])
Date: 2023-01-10 10:15:56

> On 9. Jan 2023, at 23:13, Gavin Lambert via Boost <boost_at_[hidden]> wrote:
> 
> If so, that doesn't seem like an unusual feature -- https://clang.llvm.org/extra/clang-tidy/checks/modernize/pass-by-value.html strongly encourages that constructors accept movable values by value, which will always move-from them even if the constructor later throws. (If the parameter type's move/copy constructor throws then it gets more complicated, though move constructors at least are typically expected to not throw.)

Thanks for that pointer. Yes, this was the advice I meant.