Warning

This post was published 157 days ago. The information described in this article may have changed.

Info

This post is auto-generated from RSS feed The Rust Programming Language Forum - Latest topics. Source: Pinned-scope - soundness review

Repo: Scope for async based on limited sharing and structured concurrency.

Base idea:

• Scope cannot borrow data from outside (can share only owned data) → it can be safely leaked
• Is !Unpin → cannot be moved after first poll
• Child tasks have to be fully structured → can't be leaked or dropped and have to be driven to complete to compile.

As of right now i didn't add any panic safety.

Would appreciate if someone could review soundness of unsafe in the repo.

Differences to other async scope crates:
moro / safe-async-scoped - child tasks can run in parallel
async-scoped - does not block the parent thread

1 post - 1 participant

Read full topic

🏷️ Rust_feed