rgrinberg has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
motherfsck has quit [Ping timeout: 256 seconds]
Serpent7776 has joined #ocaml
motherfsck has joined #ocaml
domq has joined #ocaml
domq has quit [Ping timeout: 268 seconds]
domq has joined #ocaml
bartholin has quit [Quit: Leaving]
domq_ has joined #ocaml
domq has quit [Ping timeout: 276 seconds]
domq_ is now known as domq
average has joined #ocaml
domq has quit [Ping timeout: 264 seconds]
domq has joined #ocaml
alexherbo2 has joined #ocaml
dhil has joined #ocaml
dnh has joined #ocaml
domq has quit [Quit: domq]
domq has joined #ocaml
dnh has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dnh has joined #ocaml
average has quit [Quit: Connection closed for inactivity]
troydm has quit [Quit: What is Hope? That all of your wishes and all of your dreams come true? To turn back time because things were not supposed to happen like that (C) Rau Le Creuset]
troydm has joined #ocaml
trev has quit [Quit: trev]
trev has joined #ocaml
domq has quit [Quit: domq]
dhil has quit [Ping timeout: 268 seconds]
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has quit [Remote host closed the connection]
pi3ce has quit [Quit: No Ping reply in 180 seconds.]
pi3ce has joined #ocaml
edr has joined #ocaml
szkl has quit [Quit: Connection closed for inactivity]
dhil has joined #ocaml
azimut has quit [Ping timeout: 240 seconds]
azimut has joined #ocaml
ridcully_ has quit [Quit: WeeChat 4.1.1]
ridcully has joined #ocaml
szkl has joined #ocaml
chrisz has quit [Quit: leaving]
chrisz has joined #ocaml
<trev>
what's the proper way to get around having slow inline_tests? ex. on my advent of code i have one lib module per day, and now it's getting slow to do `dune runtest` since it's running all those tests. at first i thought it was smart enough to determine if the tests should even be run by looking at file modifications or something, but it appears it doesn't
<trev>
should i reorganize into having a dune file per day and have each day in a subdir off of /lib ?
midgard has left #ocaml [#ocaml]
azimut has quit [Ping timeout: 240 seconds]
<discocaml>
<JM> I have a similar setup, and dune doesn't rerun old tests unless I run `dune clean`.
<greenbagels>
> Consuming (a prefix of) the sequence cycle xs once can cause the sequence xs to be consumed more than once. Therefore, xs must be persistent.
<greenbagels>
Reading about Seq.cycle; so does this mean the argument i give to cycle has to be a binding that exists as long as the return value of cycle?
<companion_cube>
it means that the sequence you give to Seq.cycle must be traversable multiple times
<greenbagels>
hmm
<greenbagels>
so basically `let new_seq = make_seq () |> Seq.cycle` would be problematic if make_seq () returns a finite sequence?
ehrt74 has joined #ocaml
<greenbagels>
i guess i dont see what would make a sequence not traversable multiple times; if the elements depends on side effects?
<companion_cube>
yes, for example something coming from a file descriptor
<companion_cube>
no `make_seq()` can return a finite sequence (otherwise cycle would be useless) but it'll be traversed many times
<greenbagels>
Right; I guess my brain is still stuck thinking about scoping in C-like languages haha
<companion_cube>
e.g. `let r=ref 0 in Seq.of_dispenser (fun () -> incr r; if !r > 10 then None else Some !r)`
<companion_cube>
this is traversable only once
<greenbagels>
companion_cube: oh also i guess they define what persistent means at the top of the module...
<greenbagels>
oops
<greenbagels>
thanks for answering despite that :p
<companion_cube>
... did I dream up changes to %S ???