How to use non-sendable types with task group?

Sometimes, I want to use a task group, but also want to use a non-sendable type in one of the group's tasks. Currently this does not seem to be possible. In general, I was wondering, shouldn't it be possible to bind an entire group, or some tasks of the group to a single isolation domain / serial executor? Of course this would mean that tasks could not actually run in parallel. However, for some I/O bound tasks, this might still be absolutely fine and I would be able to use a non-sendable that is bound to the same isolation domain. :thinking:

2 Likes