Eric Niebler

I suppose if an iterator had `any_system_tag` as its system tag, then this diff would change its reported system from host to device. :thinking: @allisonvacanti, do any iterators use `any_system_tag`?

The problem is that the io_uring_context can propagate errors of two types: `std::exception_ptr` and `std::error_code`. `any_sender_of` is only able to handle `std::exception_ptr`. There currently isn't a generalization of `any_sender_of` than...

Not those changes exactly, since that would lead to unnecessary code bloat for the vast majority of senders, which _don't_ send `std::error_code` through the error channel. The `io_uring_context` is maintained...

That would be one simple fix. Another is to put that logic into the type erased receiver itself so that any errors that are not already exception_ptrs get wrapped.

With specific regards to `.set_value/error/done()`, I'm not a huge fan of dropping support for customization-via-member-function. I like the ability to implement algorithms with custom receivers by defining receiver member functions....

Are you compiling with `/std:c++latest`?

Pass `-DCMAKE_CXX_STANDARD:STRING=20` to CMake and try again.

Do we really want to merge my change to `get_scheduler` to make it possibly `noexcept(false)`? Lewis' feedback is that that is going to be problematic, and I haven't had a...

It is hard to know who is using what open source project. Most of Facebook's mobile apps on the major platforms now use libunifex. I'm also aware of other projects...

Yes, we need more simple examples, and a simple `scheduler` example would be very enlightening. You're not far off here. One mistake you're making is that you're calling the receiver...