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

5.8.0.tar.gz
md5=2682558f405ab7c8638eeb16d0f9f46f
sha512=7f6548a1b1dbfdbc98d9352151ca7be97fa2ab63dbcc429208ce8d08308eee13f7fce31e0cca53f8880233959a60212d622270dd51bf164c3ee272f179769bd9

Description

Published: 24 Oct 2024

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 determined 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:

open Lwt.Syntax

let () =
  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 -linkpkg example.ml && ./a.out *)

In the program, functions such as Lwt_io.write create promises. The let* ... in construct is used to wait for a promise to become determined; the code after in is scheduled to run in a "callback." 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 in /r/ocaml, and 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 >= "5.7.0" & < "6.0.0"
  2. ppxlib >= "0.16.0" & < "0.36.0"
  3. ocaml >= "4.08"
  4. dune >= "1.12"

Dev Dependencies

None

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

Conflicts (2)

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