On Sun, 23 Aug 2026 at 00:53, Henry Skoglund via Std-Proposals
<std-proposals_at_[hidden]> wrote:
>
> > For ergonomics, I'd prefer an inferface where redact returns
> > std::remove_reference_t<T>&& like std::move and unredact returns T& so
> > that one could do:
> Thank you, pretty nice idea. As long as std::unredact() follows the same
> playrules as std::redact():

It's a nice idea, yes. Ted is completely correct that it's a nice
idea, and could be useful for some cases.

I'm not even against Ted's idea. I just want to suggest that we keep in mind

return -ENOTENOUGHBANGFORTHEBUCKESPECIALLYFORTHECOMPLEXITY;

I seriously don't have a strong opposing viewpoint here. Being able to
poison name lookup seems handy.
Being able to poison the lookup and then unpoison it.. ..seems..
..questionable. The former I could explain.
The latter.. ..I would struggle to explain.