Skip to content

Split deadlock #685

Closed
Closed

Description

@George-Miao

Activity

  1. Berrysoft commented on Feb 14, 2026

    @Berrysoft
    Member

    Is it really an issue of split? The example in the discussion uses BiLock instead of split.

  2. George-Miao commented on Feb 14, 2026

    @George-Miao
    MemberAuthor

    Is it really an issue of split? The example in the discussion uses BiLock instead of split.

    They are the same, generally.

  3. added theissue type on Feb 15, 2026
  4. pinned this issue on Feb 21, 2026
  5. Berrysoft commented on Mar 2, 2026

    @Berrysoft
    Member

    I don't think that it's a solvable problem with our current traits.

  6. unpinned this issue on Mar 4, 2026
  7. pinned this issue on Apr 13, 2026
  8. added this to the v0.19 milestone on Apr 13, 2026
  9. Berrysoft commented on Apr 13, 2026

    @Berrysoft
    Member

    We need to solve the split-related problems before 0.19 being released.

    • AsyncRead + AsyncWrite could not be splitted easily with BiLock.
    • The compat AsyncStream needs the inner stream's shared reference to impl AsyncRead + AsyncWrite for safety.
    • TlsStream doesn't impl AsyncRead / AsyncWrite for its shared reference.
  10. Berrysoft commented on Apr 20, 2026

    @Berrysoft
    Member

    The problems above have been solved.

  11. unpinned this issue on Apr 20, 2026
  12. Berrysoft commented on Apr 20, 2026

    @Berrysoft
    Member

    Just a comment: I don't think the bug has been solved perfectly. It's just shadowed by the futures compatible implementations.

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

    bugSomething isn't workingpackage: ioRelated to compio-io

    Type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions