-
Notifications
You must be signed in to change notification settings - Fork 8
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
Add capture_buffer
option
#23
Conversation
This is the same as #22, just as an officially documented feature |
I'm fine with it just being an documented keyword like this. It's not really changing the complexity of the implementation much. |
I agree, I think this is perfectly fine to have as a proper feature, to give users a bit more power. Could we just have a few simple tests, preferably also one that interacts with #23, and a CHANGELOG note? |
Will do! Agreed on the test, so we should probably merge #23 first, and I'll rebase and adapt this PR, afterward. |
Giving a non-standard `capture_buffer` allows to dynamically process the captured output in arbitrary ways. For example, a custom buffer may discard part of some very large output. The object passed as `capture_buffer` must implement two methods: `Base.write(capture_buffer, bytes)` and `bytes = Base.take!(capture_buffer)`.
09e69a1
to
6495de7
Compare
97b174a
to
e5dcd3d
Compare
e5dcd3d
to
c9db784
Compare
Ok, rebased, added test and documentation for how Should be good to go! |
Giving a non-standard
capture_buffer
allows to dynamically process the captured output in arbitrary ways. For example, a custom buffer may discard part of some very large output. The object passed ascapture_buffer
must implement two methods:Base.write(capture_buffer, bytes)
andbytes = Base.take!(capture_buffer)
.Closes #21