tobil4sk

Ok, I think this may be a windows specific issue (I can't reproduce it on Linux at least). When the checkout command fails, we throw an exception, but forget to...

> That would likely break a lot of things.. 🤔 However I do think this shouldn't be allowed with null safety enabled Could we make it so that `Null` never...

If a name is reserved, haxe should automatically rename it so that the generated code works. See for example what is done for hashlink: #11419. It's strange that the type...

> how was this one looking? Should I add tests for this? Yes please, a test would be useful!

I don't think that PR would solve this issue, since it will only affect the behaviour library resolution within `run.n` so it shouldn't have an effect outside of that. I...

While we're here, there is also another relevant problem I would like to solve, related to #529 and #568. Haxelib names are case insensitive but defines are case sensitive. This...

The issue is that currently there is nothing preventing someone creating a haxelib with a name that clashes with a built-in haxe define flag. Setting the flag with the `lib.`...

> Who in their right mind would want to publish a library that clashes with the compiler's defines I'm more concerned about this happening unintentionally. There are a lot of...

Here is a sample that has been stripped down further: ```haxe abstract Object(Dynamic) from Dynamic to Dynamic { @:op(A + B) private static inline function __add(a:Object, b:Object):Dynamic { if (a...

> Adds a file system check for a .haxelib directory in GlobalScope.hx (there's no LocalScope.hx class), and then sets isLocal accordingly. The `isLocal` member in the Scope class refers to...