Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

drop_value algorithm naming #1391

Open
msimberg opened this issue Jan 28, 2025 · 0 comments
Open

drop_value algorithm naming #1391

msimberg opened this issue Jan 28, 2025 · 0 comments
Labels

Comments

@msimberg
Copy link
Contributor

There's potential for misunderstandings with the current drop_value sender adaptor. It's currently implemented with the semantics of then([](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 the drop_value name could be then([](auto...) {}).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Backlog
Development

No branches or pull requests

1 participant