Wrapping C++ async APIs in Rust futures #67
Labels
good first issue
Good for newcomers
help wanted
Extra attention is needed
status-quo-story-ideas
"Status quo" user story ideas
Cancellation is the hard part here, because dropping a C++ task is undefined behavior while in Rust this is idiomatic. C++ tasks can close over non-owning references that are expected not to go away while the operation is in flight, so this is important. We want to make C++ async APIs easy to use with as little runtime overhead as possible.
The text was updated successfully, but these errors were encountered: