<d_bot>
<zakkor> Weird stuff. So I had 4.12.0 installed, I noticed 4.13 exists so I installed that. That works fine with no warning, but it seems that reason is not compatible with 4.13 yet. So I tried wiping the 4.12 folder and reinstalling it again (4.12.1 this time), and now I get those warnings again (used to get 6, now there's thousands)
Haudegen has quit [Ping timeout: 260 seconds]
wyrd has quit [Remote host closed the connection]
waleee has quit [Ping timeout: 250 seconds]
waleee has joined #ocaml
wyrd has joined #ocaml
vicfred has quit [Quit: Leaving]
waleee has quit [Quit: WeeChat 3.4]
ouestbillie has quit [Ping timeout: 256 seconds]
waleee has joined #ocaml
ouestbillie has joined #ocaml
cedric has quit [Quit: Konversation terminated!]
rgrinberg has joined #ocaml
<d_bot>
<Et7f3> reason support 4.13 but not published yet: multiple workaround add your opam repository with latest reason. Use esy and resolution.
humasect has joined #ocaml
humasect has quit [Remote host closed the connection]
hackinghorn has quit [Read error: Connection reset by peer]
hackinghorn has joined #ocaml
waleee has joined #ocaml
mbuf has quit [Quit: Leaving]
foo303 has quit [Quit: Leaving]
ski has quit [Ping timeout: 256 seconds]
dalek-caan has joined #ocaml
vicfred has joined #ocaml
vicfred_ has joined #ocaml
<olle>
Are pure functions always composable?
<Corbin>
Yes, depending on what "pure" means.
<olle>
Referenstial transparent is good enough
vicfred has quit [Ping timeout: 240 seconds]
<olle>
referential?
<olle>
Hm, size and nr of args should affect composability too
Haudegen has quit [Quit: Bin weg.]
rgrinberg has joined #ocaml
Corbin has quit [Ping timeout: 268 seconds]
sleepydog has quit [Ping timeout: 256 seconds]
sleepydog_ has joined #ocaml
Corbin has joined #ocaml
mro has joined #ocaml
mro has quit [Remote host closed the connection]
waleee has quit [Ping timeout: 250 seconds]
humasect has quit [Remote host closed the connection]
humasect has joined #ocaml
vicfred_ has quit [Quit: Leaving]
<d_bot>
<Ulugbek> When pinning a package, say `opam pin add dune.3.0.0 ...`. What does it mean to pin a package using a version number `dune.3.0.0`, specifically? Are the sources fetched and installed simply treated as for dune v3 or there's some cut-off by tags, etc. Why when I pin without a specific version 2.9.1 is pinned? When is version `dev` pinned and how's it different from 3.0.0 which is also unreleased? (there's a tag `3.0.0+alpha`)
<olle>
Maybe a metric for composability would be the ratio of pure functions :d
<hannes>
Ulugbek: as far as I understand: opam pin add dune --dev will use the dev-repo from the known opam file (in opam-repository) for dune and use that for installation -- keeping the version number to the latest known to opam
<hannes>
Ulugbek: "opam pin add dune.2.3.4" will go and download version 2.3.4 from opam repository and install it
<hannes>
Ulugbek: "opam pin add dune.3.0.0 --dev" will use the version number 3.0.0 and the dev-repo of dune.
<Corbin>
olle: Oh, maybe my last message didn't come through? Purity helps a little, but there are reasonable definitions of "pure function" that aren't computable, or aren't computable under certain compositions.
<olle>
17:48 < Corbin> Yes, depending on what "pure" means.
<olle>
Corbin: That was your last message on my machine
<olle>
Corbin: I'm thinking in business setting, not academy :)
<Corbin>
olle: Ah, noodles. ISTR I said something like: partial computable functions are composable, yes. Total computable functions are usually still total under composition, but e.g. recursion can create partial functions from total primitives.
<olle>
Hm
<d_bot>
<Ulugbek> hannes: thanks heaps! that's very useful to know
<d_bot>
<NULL> As for why the error message is cryptic, I don't know
<d_bot>
<glennsl> Ah, thanks! But yeah, I struggle to understand how the compiler arrived at that error message...
rgrinberg has joined #ocaml
olle has joined #ocaml
mro has joined #ocaml
rgrinberg has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
mro has quit [Read error: Connection reset by peer]
mro_ has joined #ocaml
lispy has left #ocaml [#ocaml]
gdd has quit [Ping timeout: 250 seconds]
gdd has joined #ocaml
<d_bot>
<d4hines> What's the status ocaml-lsp-server and OCaml 5.0? I'm trying to use the `Lwt_domain` module but I can't get it to work on anything except 5.0, but we can't upgrade until we have language server support. Does anyone know of a working fork?
mro_ has quit [Remote host closed the connection]
mro has joined #ocaml
dalek-caan has quit [Quit: dalek-caan]
<d_bot>
<octachron> OCaml 5.0 is currently a development version on the compiler repository, we are still month(s) away from a *first alpha release*. There is simply no support for ocaml-lsp-server on OCaml 5.0 yet.
<d_bot>
<octachron> (even if updating tools from 4.14 to 5.0 should be relatively swift since there is no AST differences between the two versions).
<d_bot>
<NULL> What's preventing the current version to work (at least experimentally) on the trunk version ?
<d_bot>
<octachron> Time?
<d_bot>
<octachron> The current version of Merlin generally cannot work on trunk.
<d_bot>
<octachron> There was still major work on updating Merlin for 4.14 last week.
<d_bot>
<NULL> What's the technical version why merlin for 4.14 couldn't work without modification on 5.0/trunk code ?
rgrinberg has joined #ocaml
<d_bot>
<octachron> There is no way that Merlin for 4.13 could work on trunk. Merlin use the internal typechecker API (a fact a fork of this API) which is not stable at all . Trying to use a previous version of Merlin on trunk is nearly certain to fail.
<d_bot>
<octachron> It happens that for the twin 4.14/5.0 releases, the 4.14 version of Merlin should work on 5.0; but that still requires work to check that this is indeed completely the case.
rgrinberg has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]