00:05 <companion_cube> Oh wow

00:05 <companion_cube> What's the limit on these?

00:15 <discocaml> <abstract.domain> at most 250 isn't it?

00:28 <companion_cube> .... That's quite a lot already :D

14:19 <discocaml> <cswine> do people use angstrom? Ive heard many use menhir

14:43 <companion_cube> Menhir is for languages, mostly. Angstrom can be used for things like protocols, serialization formats, etc

15:08 <discocaml> <._null._> IIRC, Coq extraction also has the issue of non-constant constructors, but as it compiled to an intermediate language (OCaml lambda I think) and the limit is only enforced at parsing, they had trouble figuring everything out

15:52 <discocaml> <Ada> httpaf is pretty popular

19:33 <discocaml> <regularspatula> c-cube: 246 is the limit

19:49 <companion_cube> That's not bad!

19:57 <discocaml> <lukstafi> How expensive is it to run `Domain.cpu_relax ()` in an (infinite) loop?

20:00 <companion_cube> I only do it for extremely short loops

20:10 <sadiq> why would you want to call it in an infinite loop?

20:25 <discocaml> <lukstafi> In terms of either taking CPU resources from the system, or energy consumption.

20:27 <discocaml> <lukstafi> @sadiqj a very primitive worker implementation -- spinup all domains.

20:28 <discocaml> <lukstafi> ```ocaml

20:28 <discocaml> <lukstafi> let spinup_device ~ordinal =

20:28 <discocaml> <lukstafi> let next_task = ref None in

20:28 <discocaml> <lukstafi> let keep_spinning = ref true in

20:28 <discocaml> <lukstafi> let worker () =

20:28 <discocaml> <lukstafi> while !keep_spinning do

20:28 <discocaml> <lukstafi> Option.iter !next_task ~f:(fun f ->

20:28 <discocaml> <lukstafi> f ();

20:28 <discocaml> <lukstafi> next_task := None);

20:28 <discocaml> <lukstafi> Domain.cpu_relax ()

20:28 <discocaml> <lukstafi> done

20:28 <discocaml> <lukstafi> in

20:28 <discocaml> <lukstafi> { next_task; keep_spinning; ordinal; domain = Domain.spawn worker }

20:28 <discocaml> <lukstafi> ```

20:40 <discocaml> <lukstafi> I'm hoping safety comes from the fact that work manager runs sequentially on the main domain.

20:59 <sadiq> I guess that works if you don't mind burning loads of CPU

21:01 <sadiq> domainslib has some quite heavily optimised data structures you could use instead: https://github.com/ocaml-multicore/domainslib/blob/main/lib/

22:00 <Inline> i want to change opams handling of my PATH variable

22:01 <Inline> i edited .opam/opam-init/variables.sh to append rather prepend the path but still no go

22:01 <Inline> as soon as i source /etc/profile all is back to prepend

22:01 <Inline> do i have to restart in order for that to take effect ?