-
-
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
[Doc] Documentation for IOContext
required
#16763
Labels
domain:docs
This change adds or pertains to documentation
domain:io
Involving the I/O subsystem: libuv, read, write, etc.
Milestone
Comments
tkelman
added
domain:docs
This change adds or pertains to documentation
domain:io
Involving the I/O subsystem: libuv, read, write, etc.
labels
Jun 5, 2016
16 tasks
JeffBezanson
added a commit
that referenced
this issue
Jul 21, 2016
JeffBezanson
added a commit
that referenced
this issue
Jul 22, 2016
JeffBezanson
added a commit
that referenced
this issue
Jul 22, 2016
RFC: improve docs for `IOContext`. fixes #16763
mfasi
pushed a commit
to mfasi/julia
that referenced
this issue
Sep 5, 2016
also remove some references to the removed `multiline` property
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
domain:docs
This change adds or pertains to documentation
domain:io
Involving the I/O subsystem: libuv, read, write, etc.
It seems like
IOContext
should be a good vehicle for specifying the output for user-defined types, e.g. here.However, without documentation of how it works, this is not possible, so package writers resort to ad-hoc solutions, such as the
displaymode
function visible at the above link.The text was updated successfully, but these errors were encountered: