tobil4sk

> After thinking on it a bit, I've added just SDL_GetJoysticks under a separate section that can be expanded later. The Heaps PR is now just a version check that...

The reason is that haxelib used to have buggy behaviour when it came to case sensitivity in library resolution, which has now been fixed. For example, if you had `hxcpp`...

I think this needs to be updated too: https://github.com/openfl/lime/blob/17fe04721d8bc4c8b18c1e3d4983b9371326e72d/src/lime/system/JNI.hx#L470 Also, this will have the same issue as the [openfl dictionary size PR](https://github.com/openfl/openfl/pull/2801) since haxe 5 preview 1 didn't have this...

The way I'm using it is to always use `InterfaceMultiaddrsFor` instead of `InterfaceMultiaddrs`, which allows any api to be used to get the addresses. I'm quite new to go so...

> Can you show me how you'll use this change? I'm having a hard time understanding how exposing InterfaceMultiaddrsFor helps here. Thanks Instead of relying on `InterfaceMultiaddrs`, a slice of...

Eval had this issue and it was considered to be a bug: https://github.com/HaxeFoundation/haxe/issues/10825

Here is a more stripped down sample (adapted from #1092): ```haxe function main() { final array:Array = []; cpp.Pointer.ofArray(array); trace(array.length); // 1 } ``` `cpp.Pointer.ofArray` does `&array[0]`, and the native...

It seems like there are a lot of weird edge cases with how lime interacts with local `.haxelib` repositories, and it's starting to get a bit difficult to keep track...

Prior to #1873, `Haxelib.workingDirectory` was set prior to running `Haxelib.getPath`, so this patch solves a regression (though, it does not occur with 8.2.3 because run.n hasn't been rebuilt). Here is...

> Oops! Looks like we've overlooked that for a while now. I just added commit https://github.com/openfl/lime/commit/49d81a6cf5cb5f269faf720298e66135c3a6bb21 to have GitHub Actions build run.n. We also need a way to keep the...