Fabian

Let's close this: It's tricky to reproduce and I don't use the hardware any more.

Note that this will break existing demangling implementations, producing non-ascii characters (due to the use of `$xx` encoding). At least on Linux, I'd suggest keeping the existing `.` separator (in...

> Could you provide more detail about which demangling implementations you mean? I am aware that Linux perf needs updating. Here is another one: https://github.com/mstange/samply/blob/bb0dbdf13f10dc22036ef2dc4ead35b9647717d6/samply-symbols/src/demangle_ocaml.rs I'd assume all demangling implementations...

> Not having used it did that project break with the change from `__` to `.` separators? No, the `.` was already printed as-is in the original implementation. > Would...

> Apologies for the naïve question: are there that many demanglers around? I'm not aware of any other demanglers except the ones already mentioned in this thread. > I also...

Note that [musl's memcmp](http://git.musl-libc.org/cgit/musl/tree/src/string/memcmp.c) is not optimised, and will likely run much slower than OCaml's current implementation.

> My only question is what to do if we've already started it from an OCAML_RUNTIME_EVENTS_START environment variable? If `OCAML_RUNTIME_EVENTS_START` is set, `Runtime_events.start` already doesn't do anything in the current...

I suggest the following way forward then: - If `OCAML_RUNTIME_EVENTS_START` is not set, calling `Runtime_events.start` doesn't create an events file. Any cursors for the event ring of the current program...

After `!`, ocaml-lsp should offer to complete references, but it offers operators starting with `!` (technically fine, but the former behavior is mostly what you want when typing `!`). If...

This seems to be fixed in most cases. ```ocaml open Base let _ = String. (* works *) ``` ```ocaml module Foo = struct (* ... *) end;; Foo. (*...