00:40 <discocaml> <sotesukeyamaha> I learned it this semester and I had a blast. For me, what's really fun about programming in OCaml is the language is a lot closer to how I think about problems. In particular, a lot of structures are easily solved with recursion but in other languages it's not as natural. It can be a pain to debug but never had this issue so far in OCaml. Most of the time, the things I write give the intended result on the first try. I also love how ex

00:40 <discocaml> <sotesukeyamaha> I learned it this semester and I had a blast. For me, what's really fun about programming in OCaml is the language is a lot closer to how I think about problems. In particular, a lot of problems with data structures are easily solved with recursion but in other languages it's not as natural. It can be a pain to debug but never had this issue so far in OCaml. Most of the time, the things I write give the intended result on the first try.

03:40 <discocaml> <dubious245> First time using it this semester and its been a joy so far.

12:38 <discocaml> <froyo> I have a bunch of effectful computations scattered across an executable's main module, with a bunch of definitions relying on effects executing before them

12:38 <discocaml> <froyo> It's basically quite imperative and fiddly but that's fine because it's just the executable

12:38 <discocaml> <froyo> Many parts of the code raise a custom exception which I want to catch globally and give the user die-style error messages that way

12:39 <discocaml> <froyo> Now I could put everything behind functions and pass around values instead of mutating globals etc etc so that I can collect everything in the last part of the module and wrap it in a try block, or I could, instead of raising an exception, just print and call exit, but I wanted to try Printexc.set_uncaught_exception_handler because why not

12:40 <discocaml> <froyo> I match on my exception and print its content, followed by a flush as the docs suggest, and on any other exception I call default_uncaught_exception_handler

12:41 <discocaml> <froyo> the handler doesn't seem to trigger. does it not trigger when the exception is raised with `raise_notrace`?

12:41 <discocaml> <froyo> nvm it doesn't seem to trigger either way

13:30 <discocaml> <froyo> here's a reproduction. I think I just don't understand how to use this function. https://tio.run/##ZY@xEoIwEER7vmKHSgv9AQc7e/8gE8lBMoaEyV1GCv8dA4KN7d7bvd3Y6sHPM00tjeJiwC2lmBA7sCQX@sqTgFaN0SBpx4TDF@LjelVoKuBeaCkxZyZRObQ691bUL1dZHYynhAf1LqDLATThIThdixkYtLR2kV5O7Kq8typcEIxLuqIS4QKBL@h8Zls6mphlw9U/WBvqdPaC/bszT0RvEJfZdTEWch@xzayFWOp5/gA

13:50 <discocaml> <octachron> The function doesn't work in REPLs, because REPL needs to handle uncaught exceptions by themselves.

13:50 <discocaml> <octachron> Outside of REPLs, your example works fine.

13:51 <discocaml> <froyo> calling ocaml on a file.ml still goes through the repl's handlers? I was under the impression it sets those up only when we're interactive.

13:51 <discocaml> <octachron> Note also that if you just want error messages, you can use the `register_printer` function

13:52 <discocaml> <octachron> `ocaml script.ml` execute the script in the REPL environment.

13:53 <discocaml> <froyo> yeah but register_printer still prints `Exception:` before calling the custom printer

13:54 <discocaml> <froyo> in any case, thanks octachron that's what I needed to know

18:07 <discocaml> <gabyfle> Hi, let say I have a bigarray allocated like this:

18:07 <discocaml> <gabyfle>

18:07 <discocaml> <gabyfle> `bigarray = caml_ba_alloc(type_flag | CAML_BA_C_LAYOUT, ndims, NULL, dims);`

18:07 <discocaml> <gabyfle>

18:07 <discocaml> <gabyfle> is there a way for me to tell OCaml to resize the bigarray into something smaller afterwards ?

18:08 <discocaml> <gabyfle> Hi, let say I have a bigarray allocated like this:

18:08 <discocaml> <gabyfle>

18:08 <discocaml> <gabyfle> `bigarray = caml_ba_alloc(type_flag | CAML_BA_C_LAYOUT, ndims, NULL, dims);`

18:08 <discocaml> <gabyfle>

18:08 <discocaml> <gabyfle> is there a way for me to tell OCaml to resize the bigarray into something smaller afterwards ? something that would no necessite a full allocation of a smaller bigarray

18:11 <discocaml> <gabyfle> I'm wondering what happens if I just change the dims using `Caml_ba_array_val(bigarray)->dims[i] = something_smaller`, is this "legal" ?

18:16 <discocaml> <gabyfle> to be clear, I build a bigarray with a shape of `(channels, samples)`, but for some formats (like MP3 for example) I might end up over estimating the number of samples per channels (it's not that huge usually, few samples)

18:23 <companion_cube> You can just take a slice of the bigarray

18:23 <companion_cube> It won't reallocate it

18:28 <discocaml> <gabyfle> yes but it's not available as an FFI function (the slicing)

18:28 <discocaml> <gabyfle> yes but it's not available as an FFI function (the slicing) (at least the bigarray.h header don't expose it)

18:59 <companion_cube> Oh. No idea.