Skip to content

std::io::{empty, sink} do not replace /dev/null #24235

Closed

Description

In particular, splitting up the Read and Write halves mean that you can't use these in a generic context that expects a full stream (Read + Write).

We should consider deprecating these in favor of a single null constructor that is both Read and Write.

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

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