Upgrade ocamlformat to 0.27.0

Author: polytypic

.ocamlformat

@@ -1,4 +1,4 @@
 profile = default
-version = 0.26.2
+version = 0.27.0
 
 exp-grouping=preserve

lib/picos.domain/picos_domain.mli

@@ -6,12 +6,12 @@ val at_exit : (unit -> unit) -> unit
 (** [at_exit action] registers [action] to be called when the current domain
     exits.
 
-    On OCaml 5 this calls {!Domain.at_exit}.  On OCaml 4 this calls
+    On OCaml 5 this calls {!Domain.at_exit}. On OCaml 4 this calls
     {!Stdlib.at_exit}. *)
 
 val recommended_domain_count : unit -> int
 (** [recommended_domain_count ()] returns [1] on OCaml 4 and calls
-    {!Domain.recommended_domain_count} on OCaml 5.  *)
+    {!Domain.recommended_domain_count} on OCaml 5. *)
 
 val is_main_domain : unit -> bool
 (** [is_main_domain ()] returns [true] on OCaml 4 and calls
@@ -23,14 +23,14 @@ module DLS : sig
       ℹ️ On OCaml 4 there is always only a single domain. *)
 
   type 'a key
-  (** Represents a key for storing values of type ['a] in storage associated with
-      domains. *)
+  (** Represents a key for storing values of type ['a] in storage associated
+      with domains. *)
 
   val new_key : (unit -> 'a) -> 'a key
   (** [new_key compute] allocates a new key for associating values in storage
-      associated with domains.  The initial value for each domain is [compute]d
+      associated with domains. The initial value for each domain is [compute]d
       by calling the given function if the [key] is {{!get} read} before it has
-      been {{!set} written}.  The [compute] function might be called multiple
+      been {{!set} written}. The [compute] function might be called multiple
       times per domain, but only one result will be used. *)
 
   val get : 'a key -> 'a

lib/picos.thread/picos_thread.mli

@@ -8,7 +8,7 @@ module TLS : sig
   (** Thread-local storage.
 
       Note that here "thread" refers to system level threads rather than fibers
-      or domains.  In case a system level thread implementation, i.e. the
+      or domains. In case a system level thread implementation, i.e. the
       [threads.posix] library, is not available, this will use
       {!Picos_domain.DLS}. *)
 
@@ -30,7 +30,7 @@ module TLS : sig
       current thread or raises {!Not_set} in case no value has been {!set} for
       the key.
 
-      ⚠️ The {!Not_set} exception is raised with no backtrace.  Always catch the
+      ⚠️ The {!Not_set} exception is raised with no backtrace. Always catch the
       exception unless it is known that a value has been set. *)
 
   val set : 'a t -> 'a -> unit

lib/picos/intf.ocaml5.ml

@@ -10,12 +10,12 @@ module type Trigger = sig
 
       Typically the scheduler calls {{!Fiber.try_suspend} [try_suspend]}, which
       in turn calls {!on_signal}, to attach a scheduler specific [resume] action
-      to the [trigger].  The scheduler must guarantee that the fiber will be
+      to the [trigger]. The scheduler must guarantee that the fiber will be
       resumed after {!signal} has been called on the [trigger].
 
       Whether being resumed due to cancelation or not, the trigger must be
-      either {{!signal} signaled} outside of the effect handler, or {{!dispose}
-      disposed} by the effect handler, before resuming the fiber.
+      either {{!signal} signaled} outside of the effect handler, or
+      {{!dispose} disposed} by the effect handler, before resuming the fiber.
 
       In case the fiber permits propagation of cancelation and the computation
       associated with the fiber has been canceled the scheduler is free to
@@ -37,9 +37,9 @@ module type Computation = sig
   (** Schedulers must handle the {!Cancel_after} effect to implement the
       behavior of {!cancel_after}.
 
-      The scheduler should typically {{!try_attach} attach} a {{!Trigger}
-      trigger} to the computation passed with the effect and arrange the
-      timeout to be canceled upon signal to avoid space leaks.
+      The scheduler should typically {{!try_attach} attach} a
+      {{!Trigger} trigger} to the computation passed with the effect and arrange
+      the timeout to be canceled upon signal to avoid space leaks.
 
       The scheduler should measure time using a monotonic clock.
 
@@ -80,15 +80,15 @@ module type Fiber = sig
     ('b, 'r) Effect.Shallow.handler ->
     'r
   (** [resume_with fiber k h] is equivalent to
-      {{!Fiber.canceled} [Effect.Shallow.continue_with k (Fiber.canceled t) h]}. *)
+      {{!Fiber.canceled} [Effect.Shallow.continue_with k (Fiber.canceled t) h]}.
+  *)
 
   val continue : t -> ('v, 'r) Effect.Deep.continuation -> 'v -> 'r
   (** [continue fiber k v] is equivalent to:
       {[
         match Fiber.canceled fiber with
         | None -> Effect.Deep.continue k v
-        | Some (exn, bt) ->
-          Effect.Deep.discontinue_with_backtrace k exn bt
+        | Some (exn, bt) -> Effect.Deep.discontinue_with_backtrace k exn bt
       ]} *)
 
   val continue_with :
@@ -101,20 +101,19 @@ module type Fiber = sig
       {[
         match Fiber.canceled fiber with
         | None -> Effect.Shallow.continue_with k v h
-        | Some (exn, bt) ->
-          Effect.Shallow.discontinue_with_backtrace k exn bt h
+        | Some (exn, bt) -> Effect.Shallow.discontinue_with_backtrace k exn bt h
       ]} *)
 
   (** Schedulers must handle the {!Current} effect to implement the behavior of
       {!current}.
 
       ⚠️ The scheduler must eventually resume the fiber without propagating
-      cancelation.  This is necessary to allow a fiber to control the
-      propagation of cancelation through the {{!t} fiber}.
+      cancelation. This is necessary to allow a fiber to control the propagation
+      of cancelation through the {{!t} fiber}.
 
-      The scheduler is free to choose which ready fiber to resume next.
-      However, in typical use cases of {!current} it makes sense to give
-      priority to the fiber performing {!Current}, but this is not required. *)
+      The scheduler is free to choose which ready fiber to resume next. However,
+      in typical use cases of {!current} it makes sense to give priority to the
+      fiber performing {!Current}, but this is not required. *)
   type _ Effect.t += private Current : t Effect.t
 
   (** Schedulers must handle the {!Yield} effect to implement the behavior of
@@ -125,7 +124,7 @@ module type Fiber = sig
       discontinue the fiber immediately.
 
       The scheduler should give priority to running other ready fibers before
-      resuming the fiber performing {!Yield}.  A scheduler that always
+      resuming the fiber performing {!Yield}. A scheduler that always
       immediately resumes the fiber performing {!Yield} may prevent an otherwise
       valid program from making progress. *)
   type _ Effect.t += private Yield : unit Effect.t
@@ -139,7 +138,7 @@ module type Fiber = sig
       ⚠️ In case the fiber performing {!Spawn} permits propagation of cancelation
       and the computation associated with the fiber has been canceled before it
       performed {!Spawn}, the scheduler should discontinue the current fiber and
-      not spawn a new fiber.  If cancelation happens during the handling of
+      not spawn a new fiber. If cancelation happens during the handling of
       {!Spawn} the scheduler is free to either spawn a new fiber, in which case
       the current fiber must be continued normally, or not spawn a fiber, in
       which case the current fiber must be discontinued, i.e. {!spawn} raises an
@@ -151,9 +150,9 @@ module type Fiber = sig
       called.
 
       In other words, spawn should (effectively) check cancelation at least once
-      and be all or nothing.  Furthermore, in case a newly spawned fiber is
+      and be all or nothing. Furthermore, in case a newly spawned fiber is
       canceled before its [main] is called, the scheduler must still call the
-      [main].  This allows a program to ensure, i.e. keep track of, that all
+      [main]. This allows a program to ensure, i.e. keep track of, that all
       fibers it spawns are terminated properly and any resources transmitted to
       spawned fibers will be disposed properly. *)
   type _ Effect.t +=