Maybe C# got me spoiled with CancellationToken which seems like a nicer API. And, perhaps, synchronization context as well if you are writing a GUI application

Maybe C# got me spoiled with CancellationToken which seems like a nicer API. And, perhaps, synchronization context as well if you are writing a GUI application and need a render thread, to make sure you yield to the right one. Though if that's not the preferred pattern, publishing a message to a channel on one end and then reading them from another is always an option.