-
Notifications
You must be signed in to change notification settings - Fork 15
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
Atomic read and write many #4
Comments
This would be useful for me, assuming it is faster. |
I would be interested in something similar. Rather than blocking until all |
Thanks for the input! Hmmm I'm not sure what you want is possible with the
|
@twittner this may be relevant to your needs, but shortly I'm going to release a change to
Without that capability we're stuck needing to do a busy-wait. |
I think the interface for batched writes will be polymorphic, and look like:
where batch instances will be tuples of different sizes The
That would just hold on to one or sever array segments, but should allow later segments to be GC'd just as we'd like. |
A simpler, and maybe more useful function is What form to return data? A stream/array like a |
It would be straight-forward to add a function like:
that atomically reads
n
consecutive messages, blocking until all are present. This would be both faster than areplicateM_ n (readChan c)
and might be useful if you need to interleave readers that need to take consecutive chunks ofn
elements for whatever reason.Please comment if you need this.
The text was updated successfully, but these errors were encountered: