[new release] mirage-flow, mirage-flow-unix and mirage-flow-combinators (4.0.0) #24959
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Flow implementations and combinators for MirageOS
CHANGES:
close
semantics, which no longer is ashutdown `read_write
(Adapt close documentation to really close the flow. mirage/mirage-flow#49 @hannesm)
shutdown : flow -> [ `read | `write | `read_write ] -> unit Lwt.t
(@djs55 @hannesm Clear up confusion between FLOW close, shutdown mirage/mirage-flow#16 Support both FLOW.disconnect and FLOW.close mirage/mirage-flow#18 Add Mirage_flow.shutdown: flow -> [ read | write | read_write ] -> unit Lwt.t mirage/mirage-flow#48)