12:54 <discocaml_> <shiny_dev> I am a lead web3 frontend and blockchain engineer, i am looking for an opportunity to work with you.

12:55 <companion_cube> good one

13:29 <discocaml_> <limp.biskit> @admin more spam

13:31 <discocaml_> <barconstruction> Did they use the everyone ping? I got a notification

14:12 <reynir> doesn't _lead_ blabla engineer mean they already have a job?

14:24 <discocaml_> <limp.biskit> leading expert in unemployment

14:40 <discocaml_> <deepspacejohn> well, you can have a job and still be "looking for an opportunity to work with you" (IDK why I'm trying to make sense of spam)

15:55 <discocaml_> <limp.biskit> are there any pitfalls to watch out for converting a functor into a class? the context is i have a main state carrying type for HTTP transactions, which i want to have multiple implementations for different schedulers, yet still allow for code reuse in simple middleware.

15:56 <discocaml_> <limp.biskit> i haven't used the object layer outside of gui things

16:30 <discocaml_> <thisisjjasmine> is there something like google summer of code but for ocaml?

16:40 <discocaml_> <thisisjjasmine> is there something like google summer of code but for ocaml?

16:40 <discocaml_> <thisisjjasmine> edit: ok i'm seeing outreachy, thank you!

19:23 <discocaml_> <gabyfle> Any idea why does `Owl` seems to not have been widely adopted even inside the OCaml's community ? I'm using it for quite a bit now to create a little sound processing library and I just managed to port the spectral helper from matplotlib <https://github.com/matplotlib/matplotlib/blob/main/lib/matplotlib/mlab.py#L213> to OCaml in a very elegant way, and I'm always amazed how complete this library is. Everytime I'm afraid I'll need to reimpleme

20:13 <discocaml_> <kakadu18> I'm doing a parallel for using Domainslib. Are there any pitfalls about reporting progress to the starting domain? I'm trying to use 'progress' library, and it crashes with `exception Stdlib.Queue.Empty` but the stack trace doesn't look like related to this library, but mentions Domainlib a lot.

20:13 <discocaml_> <kakadu18> trace: https://github.com/craigfe/progress/pull/46

20:13 <discocaml_> <kakadu18> code: https://github.com/Kakadu/progress/blob/ocaml5-buggy/examples/ocaml5.ml

20:32 <discocaml_> <octachron> You are mutating a shared mutable state across different domains without synchronization. This can only work by accident.

20:39 <discocaml_> <kakadu18> Yes, the same issue appears when we want to count how many domain finished, and it motivates invention of atomics. But I dont' yet understand how they could help me. Maybe I actually need message passing between domains?

20:53 <discocaml_> <octachron> Using an atomic counter and calling the report function in a unique separate task should work.

23:17 <discocaml_> <limp.biskit> your queue should be locked by a mutex

23:17 <discocaml_> <limp.biskit> queue isn’t thread safe