Skip to content

Tags: mirage/mirage-flow

Tags

v5.0.0

Toggle v5.0.0's commit message
Release 5.0.0

CHANGES:

- Remove functor over Mirage_clock.MCLOCK, use mirage-mtime instead
  (#53 @hannesm)

v4.0.2

Toggle v4.0.2's commit message
Release 4.0.2

CHANGES:

- revert < coercion, shutdown is again
  ``shutdown : flow -> [ `read | `write | `read_write ] -> unit Lwt.t``
  (@reynir @hannesm)

v4.0.1

Toggle v4.0.1's commit message
Release 4.0.1

CHANGES:

- move Mirage_flow.stats and pp_stats to Mirage_flow_combinators (#51 @hannesm)
- improve documentation of expected semantics (when write promise is resolved,
  what is done to the underlying flow - addresses #4 @samoht),
  (#51 @reynir @dinosaure @hannesm)
- add < coercion to shutdown:
  ``shutdown : flow -> [< `read | `write | `read_write ] -> unit Lwt.t``
  (requested #50 @reynir, #52 @hannesm)

v4.0.0

Toggle v4.0.0's commit message
Release 4.0.0

CHANGES:

- Redefine `close` semantics, which no longer is a `` shutdown `read_write ``
  (#49 @hannesm)
- Add ``shutdown : flow -> [ `read | `write | `read_write ] -> unit Lwt.t``
  (@djs55 @hannesm #16 #18 #48)
- Remove SHUTDOWNABLE signature (@djs55 #17, rebased into #48)

v3.0.0

Toggle v3.0.0's commit message
Release v3.0.0

CHANGES:

- Remove Mirage_flow_lwt module
- Require fmt 0.8.7, cstruct 6.0.0 and avoid deprecated functions
- Compatibility with alcotest 1.4 (eta expansion of Alcotest.fail)
- Mirage_flow_combinators.forward has an additional unit argument to avoid
  unerasable optional argument warning

v2.0.1

Toggle v2.0.1's commit message
Distribution v2.0.1

v2.0.0

Toggle v2.0.0's commit message
Distribution v2.0.0

v1.6.0

Toggle v1.6.0's commit message
Distribution v1.6.0

v1.5.0

Toggle v1.5.0's commit message
release v1.5.0

Signed-off-by: Anil Madhavapeddy <anil@recoil.org>

v1.4.0

Toggle v1.4.0's commit message
Distribution v1.4.0