Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix misleading NamedPipeServer example #6590

Merged
merged 1 commit into from
May 26, 2024

Commits on May 26, 2024

  1. Fix misleading NamedPipeServer example

    The previous NamedPipeServer doc example seemed to imply that the return
    type of `NamedPipeServer::connect()` was a
    `Future<Result<some_kind_of_client>>>`, however, `connect()` returns a
    `Future<Result<()>>>`. The following line of code reopening the pipe
    would shadow the newly connected pipe immediately, making the following
    spawned task pointless. Hopefully these changes make it more clear what
    should be happening in the example.
    Tacklebox committed May 26, 2024
    Configuration menu
    Copy the full SHA
    b9d2210 View commit details
    Browse the repository at this point in the history