toastloop has quit [Read error: Connection reset by peer]
Serpent7776 has joined #ocaml
bartholin has joined #ocaml
kakadu has joined #ocaml
kakadu has quit [Quit: Konversation terminated!]
bartholin has quit [Quit: Leaving]
waleee has joined #ocaml
wingsorc__ has quit [Ping timeout: 258 seconds]
azimut has joined #ocaml
azimut has quit [Ping timeout: 240 seconds]
John_Ivan has joined #ocaml
bartholin has joined #ocaml
Tuplanolla has joined #ocaml
John_Ivan has quit [Quit: Disrupting the dragon's slumber one time too often shall eventually bestow upon all an empirical and indiscriminate conflagration that will last for all goddamn eternity.]
<discocaml>
<._null._> (The webpage isn't updated yet)
<discocaml>
<spdegabrielle> Just announced at the SIGPLAN Awards Lunch at PLDI23
Serpent7776 has quit [Ping timeout: 240 seconds]
wingsorc__ has joined #ocaml
bartholin has quit [Quit: Leaving]
greaser|q has quit [Remote host closed the connection]
greaser|q has joined #ocaml
wingsorc__ has quit [Quit: Leaving]
wingsorc has joined #ocaml
greaser|q has quit [Remote host closed the connection]
greaser|q has joined #ocaml
sagax has joined #ocaml
ski has quit [Server closed connection]
ski has joined #ocaml
Tuplanolla has quit [Quit: Leaving.]
<discocaml>
<Kati roll> Hi, any news on whether mutable field modifications dropped by the compiler will be fixed in next releases? Spent 5 hours trying to understand what's happening and it was a mutable field creation 4 calls down from function that couldn't be properly uncurried by the compiler. Warning 68 was useless in this case
<companion_cube>
Hu, is there an issue for that? :o
<discocaml>
<Kati roll> Not for this case, but for multiple others
<discocaml>
<Kati roll> Supposedly syntactic arity pr should resolve this
Techcable has quit [Ping timeout: 252 seconds]
szkl has joined #ocaml
azimut has joined #ocaml
<companion_cube>
Oh wow, I didn't know that had miscompilation impacts