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.

Sign up for GitHub

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

Jump to bottom

Network documentation incorrectly claims handles are block-buffered #173

Closed
dylex opened this issue Jun 19, 2015 · 1 comment
Closed

Network documentation incorrectly claims handles are block-buffered #173

dylex opened this issue Jun 19, 2015 · 1 comment
Assignees
@kazu-yamamoto
Labels
documentation

Comments

@dylex
Copy link

dylex commented Jun 19, 2015

In the top-level module documentation under Buffering, it says, "The Handle returned by connectTo and accept is block-buffered by default." This appears not to be true (at least for connectTo) as it just calls socketToHandle which correctly claims to return an unbuffered handle.
@winterland1989 winterland1989 mentioned this issue Jul 1, 2016
Closed
@kazu-yamamoto kazu-yamamoto self-assigned this Dec 14, 2017
kazu-yamamoto added a commit that referenced this issue Dec 15, 2017
@kazu-yamamoto
fixing doc (#173)
92df270
@kazu-yamamoto
Copy link
Collaborator

Fixed. Thanks!

kazu-yamamoto added a commit to kazu-yamamoto/network that referenced this issue Jan 29, 2018
@kazu-yamamoto
fixing doc (haskell#173)
b61245d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kazu-yamamoto kazu-yamamoto

Labels
documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dylex @kazu-yamamoto