Date: Wed, 12 Aug 2026 17:51:39 +0300
On 12 Aug 2026 17:44, Ville Voutilainen wrote:
> On Wed, 12 Aug 2026 at 17:42, Andrey Semashev via Std-Proposals
> <std-proposals_at_[hidden]> wrote:
>>
>> On 12 Aug 2026 17:04, Ville Voutilainen via Std-Proposals wrote:
>>> On Wed, 12 Aug 2026 at 16:52, Udo Steinbach via Std-Proposals
>>> <std-proposals_at_[hidden]> wrote:
>>>>
>>>> Again: Benefit?
>>>> I don't see an answer on the most important question.
>>>
>>> Three relatively-concrete use cases come to mind:
>>> 1) poisoning a variable after it's been moved from
>>> 2) poisoning a task graph after it's been launched (which in Senders
>>> is also a move, but elsewhere might not be)
>>> 3) poisoning a task completion after its result has been received
>>
>> None of these require a permanent ban of the name.
>
> What do you mean by "permanent ban of the name"?
>
> It's poisoned within a scope. Once that scope exits, there is no remaining
> permaban.
I'm not sure the scope of effect of redacting was precisely defined, but
in any case, my point is that the above use cases do not require any
name ban at all.
> On Wed, 12 Aug 2026 at 17:42, Andrey Semashev via Std-Proposals
> <std-proposals_at_[hidden]> wrote:
>>
>> On 12 Aug 2026 17:04, Ville Voutilainen via Std-Proposals wrote:
>>> On Wed, 12 Aug 2026 at 16:52, Udo Steinbach via Std-Proposals
>>> <std-proposals_at_[hidden]> wrote:
>>>>
>>>> Again: Benefit?
>>>> I don't see an answer on the most important question.
>>>
>>> Three relatively-concrete use cases come to mind:
>>> 1) poisoning a variable after it's been moved from
>>> 2) poisoning a task graph after it's been launched (which in Senders
>>> is also a move, but elsewhere might not be)
>>> 3) poisoning a task completion after its result has been received
>>
>> None of these require a permanent ban of the name.
>
> What do you mean by "permanent ban of the name"?
>
> It's poisoned within a scope. Once that scope exits, there is no remaining
> permaban.
I'm not sure the scope of effect of redacting was precisely defined, but
in any case, my point is that the above use cases do not require any
name ban at all.
Received on 2026-08-12 14:51:48
