toastal has left #ocaml [Disconnected: Hibernating too long]
Serpent7776 has joined #ocaml
toastal has joined #ocaml
waleee has joined #ocaml
toastal has quit [Ping timeout: 256 seconds]
toastal has joined #ocaml
waleee has quit [Ping timeout: 255 seconds]
bartholin has joined #ocaml
jabuxas has joined #ocaml
YuGiOhJCJ has quit [Quit: YuGiOhJCJ]
mpu has quit [Remote host closed the connection]
infinity0 has quit [Remote host closed the connection]
infinity0 has joined #ocaml
myrkraverk_ has quit [Remote host closed the connection]
myrkraverk has joined #ocaml
jabuxas has quit [Ping timeout: 240 seconds]
Serpent7776 has quit [Ping timeout: 255 seconds]
ocra8 has joined #ocaml
torretto_ has quit [Remote host closed the connection]
chiselfuse has quit [Remote host closed the connection]
torretto has joined #ocaml
chiselfuse has joined #ocaml
Serpent7776 has joined #ocaml
chiselfuse has quit [Remote host closed the connection]
chiselfuse has joined #ocaml
toastal has left #ocaml [#ocaml]
torretto has quit [Remote host closed the connection]
torretto has joined #ocaml
waleee has joined #ocaml
ocra8 has quit [Quit: WeeChat 4.2.2]
jabuxas has joined #ocaml
jabuxas has quit [Ping timeout: 260 seconds]
<discocaml>
<polytypic> BTW, Picos includes a direct-style interface to Lwt <https://ocaml-multicore.github.io/picos/doc/picos/Picos_lwt/index.html>. It allows you to use existing libraries written for Lwt while also programming in direct-style and using libraries written against the Picos interface and interoperating with other Picos compatible schedulers (running on other systhreads/domains). Here is an example using Cohttp_lwt: <https://github.com/ocaml-multic
Serpent7776 has quit [Ping timeout: 246 seconds]
<discocaml>
<polytypic> BTW, Picos includes a direct-style interface to Lwt <https://ocaml-multicore.github.io/picos/doc/picos/Picos_lwt/index.html>. It allows you to use existing libraries written for Lwt while also programming in direct-style and using libraries written against the Picos interface and interoperating with other Picos compatible schedulers (running on other systhreads/domains). Here is an example using Cohttp_lwt: <https://github.com/ocaml-multic
<discocaml>
<polytypic>
<discocaml>
<polytypic> Note that `Picos_lwt` is definitely not the fastest possible scheduler. `Picos_lwt` is mostly intended as one tool among others for gradually transitioning existing code bases using Lwt towards effects based schedulers. (The `Picos_fifos` sample scheduler, for example, is a very fast single threaded effects based scheduler.)
infinity0 has quit [Remote host closed the connection]
infinity0 has joined #ocaml
<discocaml>
<limp.biskit> god i need to read docs more closely
<discocaml>
<limp.biskit> do you know if it would run under miou?
<discocaml>
<limp.biskit> / alongside
torretto has quit [Quit: WeeChat 4.1.1]
torretto has joined #ocaml
bartholin has quit [Quit: Leaving]
<discocaml>
<dinosaure> It's probably possible. As I said, I currently copy the core of picos to build up miou then. But we can imagine a redistribution (like `miou.with_picos`) which provides exactly the same as Miou but with the picos depenendency (actually, only `miou_sync.ml` need to change) and from that you will get a fully compatible version of Miou with picos
<companion_cube>
You can use a `select` in dune to either pick picos if available, or use your vendored copy otherwise
jabuxas has joined #ocaml
Tuplanolla has quit [Quit: Leaving.]
<discocaml>
<dinosaure> Actually, what I think is just to copy miou source files without `miou_sync.ml` and do the glue. The result is: you have 2 miou (findlib) packages which exposes exactly the same thing but one depends on picos, the other is without any dependencies.
<discocaml>
<dinosaure> Actually, what I think is just to copy miou source files without `miou_sync.ml` and do the glue. The result is: you have 2 miou (findlib) packages which expose exactly the same thing but one depends on picos, the other is without any dependencies.