Nicolás Ojeda Bär
Nicolás Ojeda Bär
Do you get the segfault if you call `Fsevents.stop` outside of the callback (after `Fsevents.run_current_thread` returns)? I believe `Fsevents.stop` actually frees the associated data structure, so it shouldn't be done...
> Although they can be found in the source, it seems to me a saner approach to document them in the manual page. They can also be found by doing...
> * which tries to access `ocamlrun` in an absolute location. The non-relocatability of the toolchain is a long-standing issue; but I believe that there may be improvements coming soon...
I took a quick look at the code, and this is what I found so far. First, recall that top-level bindings are compiled differently under `ocamlopt` and `ocamlc`. Under `ocamlc`,...
> Dynlink and findlib.dynload work only in native or bytecode, but not in the top-level mode. Sorry for the naïve question, but couldn't `#require` be used to load a plugin...
> Concerning the name, I hesitated with having a more generic `experimental` or `unstable` alert. However, if the alert is adopted in various libraries, it would be harder to selectively...
> I like the idea of an API-generic `unstable` or `experimental` alert. Can we take a bit of time to discuss whether that could work? @nojb points out that it...
> That's not entirely true, you can always selectively disable the warning at the file level on a section of code using that library. Of course it's rather inconvenient it...
> We could also support `xy` to print the bytes in hexadecimal. This would actually be quite useful.