Remove left-over from Lwt_domain (now in separate repository)

Author: raphael-proust

.github/workflows/workflow.yml

@@ -27,63 +27,43 @@ jobs:
           - false
         ppx:
           - true
-        domain:
-          - false
-        local-packages:
-          - |
-            *.opam
             !lwt_domain.opam
         include:
           - os: ubuntu-latest
             ocaml-compiler: ocaml-variants.4.14.0+options,ocaml-option-flambda,ocaml-option-musl,ocaml-option-static
             libev: false
             ppx: true
-            domain: false
-            local-packages: |
-              *.opam
-              !lwt_domain.opam
+            local-packages: *.opam
           - os: macos-latest
             ocaml-compiler: 4.14.x
             libev: true
             ppx: true
-            domain: false
-            local-packages: |
-              *.opam
-              !lwt_domain.opam
+            local-packages: *.opam
           - os: windows-latest
             ocaml-compiler: 4.14.x
             libev: false
             ppx: true
-            domain: false
-            local-packages: |
-              *.opam
-              !lwt_domain.opam
+            local-packages: *.opam
           - os: ubuntu-latest
             ocaml-compiler: 4.08.x
             libev: true
             ppx: false
-            domain: false
             local-packages: |
               *.opam
-              !lwt_domain.opam
               !lwt_ppx.opam
           - os: macos-latest
             ocaml-compiler: 4.08.x
             libev: true
             ppx: false
-            domain: false
             local-packages: |
               *.opam
-              !lwt_domain.opam
               !lwt_ppx.opam
           - os: windows-latest
             ocaml-compiler: 4.08.x
             libev: false
             ppx: false
-            domain: false
             local-packages: |
               *.opam
-              !lwt_domain.opam
               !lwt_ppx.opam
 
     runs-on: ${{ matrix.os }}
@@ -112,24 +92,15 @@ jobs:
       - run: opam install lwt_ppx --deps-only --with-test
         if: ${{ matrix.ppx == true }}
 
-      - run: opam install lwt_domain --deps-only --with-test
-        if: ${{ matrix.domain == true }}
-
       - run: opam exec -- dune build --only-packages lwt_luv,lwt_react,lwt
 
       - run: opam exec -- dune build --only-packages lwt_ppx
         if: ${{ matrix.ppx == true }}
 
-      - run: opam exec -- dune build --only-packages lwt_domain
-        if: ${{ matrix.domain == true }}
-
       - run: opam exec -- dune runtest --only-packages lwt_luv,lwt_react,lwt
 
       - run: opam exec -- dune runtest --only-packages lwt_ppx
         if: ${{ matrix.ppx == true }}
 
-      - run: opam exec -- dune runtest --only-packages lwt_domain
-        if: ${{ matrix.domain == true }}
-
       - run: opam exec -- make ppx_let-test-deps ppx_let-test
         if: ${{ matrix.ppx == true }}

docs/Makefile

@@ -5,21 +5,18 @@ PKGS=\
 	-package bytes -package result \
 	-package bigarray -package unix \
 	-package ocaml-migrate-parsetree -package ppx_tools_versioned \
-	-package react \
-	-package domainslib
+	-package react
 
 INCS=\
 	-I ${BLD}/core/.lwt.objs/byte \
 	-I ${BLD}/ppx/.ppx_lwt.objs/byte \
 	-I ${BLD}/react/.lwt_react.objs/byte \
-	-I ${BLD}/domain/.lwt_domain.objs/byte \
 	-I ${BLD}/unix/.lwt_unix.objs/byte
 
 MLIS=\
 	$(wildcard ${SRC}/core/*.mli) \
 	$(wildcard ${SRC}/ppx/*.mli) \
 	$(wildcard ${SRC}/react/*.mli) \
-	$(wildcard ${SRC}/domain/*.mli) \
 	$(filter-out ${BLD}/unix/lwt_unix.cppo.mli,$(wildcard ${BLD}/unix/*.mli))
 
 MLIS := $(filter-out %.pp.mli,$(MLIS))

docs/apiref-intro

@@ -71,18 +71,6 @@ Syntactic sugar for Lwt, such as [let%lwt x = e in e'] syntax for [bind].
 Ppx_lwt
 }
 
-{2 Multicore helpers}
-
-The {e lwt_domain} package provides helpers for executing some computations on
-different cores. It is an Lwt-specific abstraction over the {e domainslib}
-package.
-
-{!modules:
-Lwt_domain
-}
-
-This package depends on the {e core} library and the {e domainslib} package.
-
 {2 Miscellaneous}
 
 The following modules are wrapper for integration of non-Lwt

docs/manual.wiki

@@ -730,30 +730,6 @@ let () =
 
 == Other libraries ==
 
-=== Parallelise computations to other cores ===
-
-  If you have some compute-intensive steps within your program, you can execute
-  them on a separate core. You can get performance benefits from the
-  parallelisation. In addition, whilst your compute-intensive function is running
-  on a different core, your normal I/O-bound tasks continue running on the
-  original core.
-
-  The module {{{Lwt_domain}}} from the {{{lwt_domain}}} package provides all the
-  necessary helpers to achieve this. It is based on the {{{Domainslib}}} library
-  and uses similar concepts (such as tasks and pools).
-
-  First, you need to create a task pool:
-
-<<code language="ocaml" |val setup_pool : ?name:string -> int -> pool
->>
-
-  Then you simple detach the function calls to the created pool:
-
-<<code language="ocaml" |val detach : pool -> ('a -> 'b) -> 'a -> 'b Lwt.t
->>
-
-  The returned promise resolves as soon as the function returns.
-
 === Detaching computation to preemptive threads ===
 
   It may happen that you want to run a function which will take time to