10:53 <discocaml> <darrenldl> @kumar I asked around on my university compsci discord, and got a response:

10:53 <discocaml> <darrenldl> "For OCaml I'd recommend learning how JS's Async library works, which is very similar to async/await in Python and JavaScript. It uses a single thread with a scheduler that (roughly speaking) loops through all the active async/concurrent functions doing a bit of work in each until they're complete. See https://dev.realworldocaml.org/concurrent-programming.html

10:53 <discocaml> <darrenldl>

10:53 <discocaml> <darrenldl> If you want to write concurrent code with multithreading, I'd probably recommend learning Rust using the Rust book (https://doc.rust-lang.org/stable/book/) and finding a good tutorial on using standard library's std::sync::{Mutex, Arc} and maybe std::sync::atomic and std::sync::mpsc. The reason I say Rust is because it gives good compiler errors for many types of memory bugs that are common writing concurrent code, so it teaches you best pra

10:57 <discocaml> <kumar> I am more of a rust person than a js/python person so thanks for the effort and help. I was using tokio, maybe understanding tokio might help. There is also https://lunatic.solutions/ which is an erlang like runtime unlike tokio which has an async-await syntax

10:59 <discocaml> <kumar> I am more of a rust person than a js/python person so thanks for the effort and help. I was using tokio so I'll go forth learning tokio, maybe understanding tokio might help. There is also https://lunatic.solutions/ which is an erlang like runtime unlike tokio which has an async-await syntax

11:00 <discocaml> <kumar> and I maybe after effects ocaml would have a different approach to concurrent programming with effects

11:00 <discocaml> <kumar> specially after eio

11:01 <discocaml> <kumar> But thanks for gathering info and resource! Again really appreciate it

11:53 <discocaml> <copy> I'd suggest building your own scheduler with the effects manual (https://v2.ocaml.org/manual/effects.html) and Uring (https://github.com/ocaml-multicore/ocaml-uring/blob/main/lib/uring/uring.mli). Both well-documented, and should give you a good idea of a modern scheduler in ~200 lines of code.

12:21 <discocaml> <darrenldl> yep it'd a more direct style (no more needing to put everything under `Lwt.t` as soon as you want to make use of one), but the general thinking about async would be similar, and you get preemptive scheduling within a domain (i'm pretty sure...)

15:02 <discocaml> <Anurag> @kumar If you are looking for examples of a simple event loop using the new effect modules in OCaml 5, I have a couple of samples that could be of interest. <https://github.com/anuragsoni/sandbox/tree/main/ocaml/effect_poll> for a single threaded loop, and <https://github.com/anuragsoni/sandbox/tree/main/ocaml/async_io> for a multi-threaded loop.

15:02 <discocaml> <Anurag>

15:02 <discocaml> <Anurag> These were for educational purposes only, so i'd still look at how Janestreet's async is structured for a more robust production ready async runtime.

17:37 <discocaml> <kumar> @copy implementation of your own scheduler sounds like a cool thing to do. Thanks for the suggestion I might just do it.

17:37 <discocaml> <kumar>

17:37 <discocaml> <kumar> @BigOof I think lwt_preemptive scheduling is also built on domains.

17:37 <discocaml> <kumar>

17:37 <discocaml> <kumar> @Anurag both samples look interesting I'll have a look thanks! I've never used async by Janestreet but I can try using it. Async is in the real world ocaml book so it's worth trying

17:37 <discocaml> <kumar> Thanks for the suggestions and help 🙏

23:14 <discocaml> <masterbuilder> is there any way to get information about local variables when debugging ocaml programs using gdb?

23:28 <companion_cube> full support for DWARF is still not there, alas

23:59 <discocaml> <masterbuilder> oh, that's too bad

23:59 <discocaml> <masterbuilder> logging it is then