-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Base.IOBuffer documentation error #23398
Comments
fredrikekre
added
docs
This change adds or pertains to documentation
io
Involving the I/O subsystem: libuv, read, write, etc.
labels
Aug 22, 2017
fredrikekre
added a commit
that referenced
this issue
Aug 30, 2017
thx @fredrikekre |
ararslan
pushed a commit
that referenced
this issue
Sep 13, 2017
vtjnash
pushed a commit
that referenced
this issue
Sep 14, 2017
ararslan
pushed a commit
that referenced
this issue
Sep 15, 2017
ararslan
pushed a commit
that referenced
this issue
Sep 16, 2017
ararslan
pushed a commit
that referenced
this issue
Sep 18, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The doc for
IOBuffer
says:IOBuffer([data,],[readable::Bool=true, writable::Bool=true, [maxsize::Int=typemax(Int)]])
The part about "by default ... not writeable" is wrong.
I'm guessing that this may have lead people to use
PipeBuffer()
instead ofIOBuffer()
when they do not needseek()
and all they are doing is a few writes to a buffer beforetake!
-ing the result.The text was updated successfully, but these errors were encountered: