package lwt_ppx

  1. Overview
  2. Docs
PPX syntax for Lwt, providing something similar to async/await from JavaScript

Install

dune-project
 Dependency

Authors

Maintainers

Sources

6.1.0.tar.gz
md5=16d58c8295b5273e58779db0ad1f967a
sha512=d5eafe2f5d2dc576b76db15b84caf69d673cb3d736dc3e40b239e6a42c6036658c78bd4b883e9f2b9f627c144be515b1824f1f2de9d79c05d5744c456fb63257

Description

Published: 03 Feb 2026

README

Lwt

version GitHub Actions status

Lwt is a concurrent programming library for OCaml. It provides a single data type: the promise, which is a value that will become resolved in the future. Creating a promise spawns a computation. When that computation is I/O, Lwt runs it in parallel with your OCaml code.

OCaml code, including creating and waiting on promises, is run in a single thread by default, so you don't have to worry about locking or preemption. You can detach code to be run in separate threads on an opt-in basis.

Here is a simplistic Lwt program which requests the Google front page, and fails if the request is not completed in five seconds:

let () =
  let request =
    let%lwt addresses = Lwt_unix.getaddrinfo "google.com" "80" [] in
    let google = Lwt_unix.((List.hd addresses).ai_addr) in

    Lwt_io.(with_connection google (fun (incoming, outgoing) ->
      write outgoing "GET / HTTP/1.1\r\n";%lwt
      write outgoing "Connection: close\r\n\r\n";%lwt
      let%lwt response = read incoming in
      Lwt.return (Some response)))
  in

  let timeout =
    Lwt_unix.sleep 5.;%lwt
    Lwt.return_none
  in

  match Lwt_main.run (Lwt.pick [request; timeout]) with
  | Some response -> print_string response
  | None -> prerr_endline "Request timed out"; exit 1

(* ocamlfind opt -package lwt.unix,lwt_ppx -linkpkg example.ml && ./a.out *)

If you are not using the lwt_ppx syntax extension, you can use the let* binding opoerators from the Lwt.Syntax module instead.

let () =
  let open Lwt.Syntax in
  let request =
    let* addresses = Lwt_unix.getaddrinfo "google.com" "80" [] in
    let google = Lwt_unix.((List.hd addresses).ai_addr) in

    Lwt_io.(with_connection google (fun (incoming, outgoing) ->
      let* () = write outgoing "GET / HTTP/1.1\r\n" in
      let* () = write outgoing "Connection: close\r\n\r\n" in
      let* response = read incoming in
      Lwt.return (Some response)))
  in

  let timeout =
    let* () = Lwt_unix.sleep 5. in
    Lwt.return_none
  in

  match Lwt_main.run (Lwt.pick [request; timeout]) with
  | Some response -> print_string response
  | None -> prerr_endline "Request timed out"; exit 1

(* ocamlfind opt -package lwt.unix,lwt_ppx -linkpkg example.ml && ./a.out *)

In the program above, functions such as Lwt_io.write create promises. The let%lwt ... in construct (provided by lwt_ppx) or the let* ... in construct (provided by Lwt.Syntax) are used to wait for a promise to resolve. The code after in is scheduled to run after the code inside the let...in has resolved.

Lwt.pick races promises against each other, and behaves as the first one to complete.

Lwt_main.run forces the whole promise-computation network to be executed. All the visible OCaml code is run in a single thread, but Lwt internally uses a combination of worker threads and non-blocking file descriptors to resolve in parallel the promises that do I/O.


Overview

Lwt compiles to native code on Linux, macOS, Windows, and other systems. It's also routinely compiled to JavaScript for the front end and Node by js_of_ocaml.

In Lwt,

  • The core library Lwt provides promises...
  • ...and a few pure-OCaml helpers, such as promise-friendly mutexes, condition variables, and mvars.
  • There is a big Unix binding, Lwt_unix that binds almost every Unix system call. A higher-level module Lwt_io provides nice I/O channels.
  • Lwt_process is for subprocess handling.
  • Lwt_preemptive spawns system threads.
  • The PPX syntax allows using all of the above without going crazy!
  • There are also some other helpers, such as Lwt_react for reactive programming. See the table of contents on the linked manual pages!

Installing

  1. Use your system package manager to install a development libev package. It is often called libev-dev or libev-devel.
  2. opam install conf-libev lwt

Documentation

We are currently working on improving the Lwt documentation (drastically; we are rewriting the manual). In the meantime:

  • The current manual can be found here.
  • Mirage has a nicely-written Lwt tutorial.
  • An example of a simple server written in Lwt.
  • Concurrent Programming with Lwt is a nice source of Lwt examples. They are translations of code from the excellent Real World OCaml, but are just as useful if you are not reading the book.

Note: much of the current manual refers to 'a Lwt.t as "lightweight threads" or just "threads." This will be fixed in the new manual. 'a Lwt.t is a promise, and has nothing to do with system or preemptive threads.


Contact

Open an issue, visit Discord chat, ask on discuss.ocaml.org, or on Stack Overflow.

Release announcements are made on discuss.ocaml.org. Watching the repo for "Releases only" is also an option.


Contributing

  • CONTRIBUTING.md contains tips for working on the code, such as how to check the code out, how review works, etc. There is also a high-level outline of the code base.
  • Ask us anything, whether it's about working on Lwt, or any question at all about it :)
  • The documentation always needs proofreading and fixes.
  • You are welcome to pick up any other issue, review a PR, add your opinion, etc.
  • Any feedback is welcome, including how to make contributing easier!

Libraries to use with Lwt

Dependencies (4)

  1. lwt >= "6"
  2. ppxlib >= "0.36"
  3. ocaml >= "4.08"
  4. dune >= "3.18"

Dev Dependencies (1)

  1. odoc with-doc

Used by (97)

  1. activitypub
  2. anthill
  3. azure-cosmos-db
  4. canary
  5. chamo
  6. chess_com_api
  7. cohttp-lwt-jsoo >= "5.3.0"
  8. css
  9. curl_lwt
  10. dap
  11. devkit
  12. docker_hub < "0.2.0"
  13. dream >= "1.0.0~alpha4"
  14. dream-encoding >= "0.2.0"
  15. dream-httpaf
  16. dream-inertia
  17. dream-livereload >= "0.2.0"
  18. dream-pure
  19. dream-serve
  20. dream_middleware_ext
  21. earlybird
  22. elasticsearch-cli
  23. eliom
  24. erssical
  25. FPauth-core
  26. gdbprofiler
  27. gremlin
  28. guardian
  29. hyper
  30. i3ipc
  31. jupyter
  32. jupyter-kernel < "0.5"
  33. lambdapi >= "2.4.0"
  34. ldp
  35. lichess_api
  36. lru_cache
  37. mehari-lwt-unix < "0.3"
  38. mehari-mirage < "0.3"
  39. menhir-lsp
  40. monorobot
  41. mpris
  42. mqtt
  43. multipart-form-data
  44. mwt
  45. naboris >= "0.1.3"
  46. neo4j_bolt
  47. noise
  48. obus >= "1.2.0"
  49. ocsipersist-lib >= "1.0.3"
  50. ojs-base
  51. ojs_base
  52. opam-check-npm-deps < "4.1.0"
  53. openai
  54. opentelemetry-client-cohttp-eio
  55. opentelemetry-client-cohttp-lwt
  56. opentelemetry-lwt >= "0.5"
  57. oraft >= "0.3.0"
  58. order-i3-xfce
  59. owork
  60. passage < "0.1.8"
  61. pgn_parser
  62. plotkicadsch
  63. ppx_cstruct >= "6.0.1"
  64. ppx_defer >= "0.4.0"
  65. qdrant < "0.2.0"
  66. qfs >= "0.7"
  67. quests
  68. rdf_json_ld
  69. rdf_lwt
  70. SZXX < "2.0.0"
  71. scgi
  72. server-reason-react
  73. sihl >= "0.6.0~rc1"
  74. slack
  75. slacko
  76. speed
  77. statocaml
  78. stk
  79. stog >= "0.19.0"
  80. syguslib-utils
  81. testcontainers
  82. testcontainers-elasticsearch
  83. testcontainers-kafka
  84. testcontainers-localstack
  85. testcontainers-memcached
  86. testcontainers-mockserver
  87. testcontainers-mongo
  88. testcontainers-mysql
  89. testcontainers-postgres
  90. testcontainers-rabbitmq
  91. testcontainers-redis
  92. textrazor
  93. tidy_email_mailgun
  94. tidy_email_sendgrid
  95. tidy_email_smtp
  96. usb
  97. ws-server

Conflicts (2)

  1. lwt = "6.0.0-beta01"
  2. lwt = "6.0.0~alpha00"