drop_value
algorithm naming
#1391
Labels
category: senders/receivers
P2300
effort: 3
A few days of work.
priority: medium
This should be done sooner or later.
type: cleanup
type: refactoring
There's potential for misunderstandings with the current
drop_value
sender adaptor. It's currently implemented with the semantics ofthen([](auto&&...) {})
, i.e. all value categories are accepted, but always by reference, so the values will actually be destroyed whenever an operation state decides that it's time to do so.An alternative name for the current semantics could be
ignore_value
. More appropriate semantics for thedrop_value
name could bethen([](auto...) {})
.The text was updated successfully, but these errors were encountered: