proportions has quit [Remote host closed the connection]
wingsorc has joined #ocaml
olle has quit [Ping timeout: 248 seconds]
kakadu_ has quit [Remote host closed the connection]
gdd has quit [Ping timeout: 265 seconds]
gdd has joined #ocaml
waleee has joined #ocaml
olle has joined #ocaml
jao has joined #ocaml
rgrinberg has joined #ocaml
motherfsck has quit [Ping timeout: 252 seconds]
count3rmeasure has quit [Read error: Connection reset by peer]
rgrinberg has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
trev has joined #ocaml
rgrinberg has joined #ocaml
rgrinberg has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
rgrinberg has joined #ocaml
<discocaml>
<MasterBuilder> I'm curious why OCaml decided against supporting "clausal function definitions" like in Haskell or Standard ML for example, `function` works but it is definitely more ugly, is there a specific reason why it's like this?
<discocaml>
<MasterBuilder> I'm curious why OCaml decided against supporting "clausal function definitions" like in Haskell or Standard ML for example, `function` works but it is definitely more ugly (at least, in my opinion), is there a specific reason why it's like this?
<discocaml>
<Gooby> I prefer not using clausal definitions, but I wondered about that as well at some point
<discocaml>
<Gooby> I assume it was just something that required effort to implement but didn't provide much
trev has quit [Remote host closed the connection]
<discocaml>
<froyo> I'm more interested in the juxtaposition between ocaml and sml where sml provides a curried pattern matching feature but the default is tupled functions, while ocaml only has tupled pattern matching abstractions when the language's default is currying.
<discocaml>
<froyo> i mean in sml that abstraction is clauses yea
<discocaml>
<froyo> but i'd expect `function` to allow currying
<discocaml>
<froyo> instead i get this: `Some Some x` works
rgrinberg has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<discocaml>
<RegularSpatula> How big of a problem in practice is the memory management when using ctypes? Eg, some of the subtleties of keeping values alive long enough as mentioned in this github issue: https://github.com/yallop/ocaml-ctypes/issues/571 .
<discocaml>
<RegularSpatula> It seems like this problem would make working with ctypes code pretty challenging, but I'm not sure
<discocaml>
<geoff> It's not too bad, but you do have to be careful of the issue that they mention. I've run into it in the past but if you follow a pattern that avoids it I don't think it's that painful
<discocaml>
<geoff> I keep the original typed ptr around, ignoring the typed ptr returned by the C function that takes the void buffer
<discocaml>
<geoff> It is definitely a gotcha though
<discocaml>
<RegularSpatula> Thanks, I will see that to my list of examples for avoiding the issue
<discocaml>
<RegularSpatula> Yeah, was playing around with tsdl, and thought, let me out a finalized on some of these things to free them. But then saw that issue and was thinking maybe just to manually manage the memory instead
<discocaml>
<RegularSpatula> *add a finalizer I mean
rgrinberg has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Serpent7776 has quit [Ping timeout: 260 seconds]
malc has joined #ocaml
cedric has joined #ocaml
Haudegen has quit [Quit: No Ping reply in 180 seconds.]
Haudegen has joined #ocaml
oriba has joined #ocaml
cedric has quit [Quit: Konversation terminated!]
rgrinberg has joined #ocaml
<discocaml>
<geoff> when the finalizer is called, ocaml is about to free the memory, so destruction is what I attach with it instead
Anarchos has quit [Quit: Vision[]: i've been blurred!]
Anarchos has joined #ocaml
Anarchos has quit [Client Quit]
spip has quit [Ping timeout: 260 seconds]
bobo has joined #ocaml
manicennui has left #ocaml [#ocaml]
<discocaml>
<ilo Kali> kind of a weird question, but does someone have a list of all functions that have side effects in the ocaml stdlib, or (even better) a way to generate one for arbitrary modules?