Skip to content

destroy/pump #283

Description

@calvinmetcalf

since pump relies on destroy, we probably want destroy in before we do pump.

Activity

  1. mcollina commented on May 10, 2017

    @mcollina
    SponsorMember

    I would say so, let's wait for nodejs/node#12925 to land.

  2. mcollina commented on Jun 6, 2017

    @mcollina
    SponsorMember
  3. calvinmetcalf commented on Jun 6, 2017

    @calvinmetcalf
    ContributorAuthor

    I have a pull I've started a bit back that I can clean up with a bit and submit it, I was waiting on destroy to land first

  4. mcollina commented on Jun 6, 2017

    @mcollina
    SponsorMember

    @calvinmetcalf I think you can fire that, and we can discuss it in the issue tracker.

  5. calvinmetcalf commented on Jun 6, 2017

    @calvinmetcalf
    ContributorAuthor
  6. calvinmetcalf commented on Jun 6, 2017

    @calvinmetcalf
    ContributorAuthor
  7. SimenB commented on Aug 21, 2017

    @SimenB
    Member

    Any news here? Or is it blocked on landing in node core? Would love to be able to just depend on readable stream 🙂

  8. mcollina commented on Aug 21, 2017

    @mcollina
    SponsorMember

    @SimenB it's just work that needs doing. Do you want to help a bit?

  9. SimenB commented on Aug 21, 2017

    @SimenB
    Member

    My understanding of stream internals are next to none, so I'm unfortunately not much help with that 🙁

  10. prog1dev commented on Mar 20, 2018

    @prog1dev
  11. added a commit that references this issue on Aug 10, 2018
    9004c81
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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions