Simon Krajewski
Simon Krajewski
Hmm, some of these might be controversial because of exceptions. For instance, `isDirectory` is documented to throw an exception in some cases, so something like this could be a pattern:...
@kLabz Could you double check these `@:pure(false)` additions? I'm fine with merging this if there's no further potential problems.
Unfortunately, this PR never got updated and would need further work, so I'll have to close it.
https://discuss.ocaml.org/t/ocaml-on-windows-the-long-paths-issue/13283 seems related.
Could you try that with latest? It's probably still going to fail but that way the stacktrace aligns with what I'm looking at.
Thanks! If I'm reading that correctly there's a constructor which the compiler thinks is a variable instead of a method... I do remember some similar problem related to the Var/Method...
Two things: 1. We try to avoid magic values like `""`, so it's better to declare `com.std_path` as `string option` and then do `(match com.std_path with None -> (* the...
This was never updated.
I wonder why you have all these unknown positions in your codebase in the first place. Some errors are going to be difficult to decorate with more useful information, so...
This issue seems to have far-reaching consequences for the overall design and makes me lean towards explicitly representing coroutines as class instances after all. While there are some advantages to...