Skip to content

futures: Write-then-transfer-read-handle does not work #1180

Closed

Description

@alexcrichton

Currently with the async runtime support for Rust if a future is created it yields a (reader, writer) end. They're both considered "local" until the reader is transferred away. If the writer has an ongoing write when the reader is transferred away then the write needs to be promoted from a local write to an intrinsic-based write. That doesn't happen today which means that the future basically gets stuck.

Activity

  1. added
    asyncRelated to async/streams in the component model.
    gen-rustRelated to bindings for Rust-compiled-to-WebAssembly
    on Feb 28, 2025
  2. alexcrichton commented on Feb 28, 2025

    @alexcrichton
    MemberAuthor

    I think specifically that today this behavior would trigger this abort because the state will be LocalReady after the write.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    asyncRelated to async/streams in the component model.gen-rustRelated to bindings for Rust-compiled-to-WebAssembly

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions