Aurea

I agree with this, I did find the target-specific sections a bit too thin. Do you have any specific suggestions apart from the compiler defines?

Isn't it a bug? AFAIK most of Haxelib should be case-insensitive. This could confuse people, it certainly confused me.

@uvtc Case-sensitivity in haxelib would cause problems on case-insensitive filesystems, not the other way around. `ALibrary` should be the same as `alibrary`, same for users, for ease of use with...

> … how having haxelib be case-sensitive would cause a problem on a case-insensitive filesystem. Could you give an example? That was the example. If there were two libraries, `ALibrary`...

I also see no reason to do client-side hashing. Using one password per platform is what users should do anyway…

I don't think HashLink can support WASM without changing the GC a lot. The collector currently scans registers and stacks, relying on `setjmp` for the former. As per [Emscripten portability...

I think I agree with OP here. Assuming a class is properly documented (as in, each method has some amount of docs), scrolling through the document to find any particular...

By the way, for large dependencies included in the repo you might want to mark them as "vendored" in the attributes: [`.gitattributes`](https://github.com/github/linguist/blob/master/docs/overrides.md#using-gitattributes)

That `font-family` should be followed by `, monospace` for a system default.

So `haxelib run hxcpp ` just invokes `bin/Cppia `. `bin/Cppia` I believe is just the binary produced by building [`cpp.cppia.Host`](https://github.com/HaxeFoundation/haxe/blob/development/std/cpp/cppia/Host.hx). Within the host, `Sys.args()` can be read, but not really...