Skip to content

Support for noncopyable Service #204

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.

Sign up for GitHub

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

Jump to bottom
Open
RandomHashTags opened this issue Apr 24, 2025 · 1 comment
Open

Support for noncopyable Service #204

RandomHashTags opened this issue Apr 24, 2025 · 1 comment
Labels
kind/enhancement Improvements to existing feature. size/M Medium task. (A couple of days of work.) status/blocked Waiting for another issue.

Comments

@RandomHashTags
Copy link

RandomHashTags commented Apr 24, 2025 •
edited
Loading

It would be nice if there was a noncopyable Service protocol as I am currently required to compromise the data structure in one of my projects heavily utilizing noncopyable types. Or at the very least make run() mutating.
@FranzBusch
Copy link
Contributor

At this point we cannot adopt ~Copyable for Services since we need move the service into a child task. Until we get call-once closures that's not going to work nicely. Let's keep this issue open for tracking purposes until the language provides such call-once closures.

@FranzBusch FranzBusch added kind/enhancement Improvements to existing feature. size/M Medium task. (A couple of days of work.) status/blocked Waiting for another issue. labels Apr 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement Improvements to existing feature. size/M Medium task. (A couple of days of work.) status/blocked Waiting for another issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@FranzBusch @RandomHashTags