tobil4sk

> Can you let me know if it's OK for mme to post on the OCaml forum, asking if anybody else wants to take this project up? @chetmurthy That's all...

> I wonder if we can just support overloading the constructor for this. Not sure if that just works already. Another option would be to just have the defaultValue as...

~~I mean with a single constructor like this, like proposed in the original issue~~ (nvm, I just saw https://github.com/HaxeFoundation/haxe/pull/9478): ```haxe public inline function new(length:Int, ?defaultValue:T) { this = new java.NativeArray(length);...

> @tobil4sk there is a problem https://github.com/HaxeFoundation/haxe/issues/10986 This is only a problem during development, no? Once the Vector constructor overload is complete, the user won't be changing the Vector class...

> Yes, but this bug reproduces even if you change any comment in something like std.StringTools So to clarify, adding the extra constructor results in future changes to other classes...

Yes, that's correct. However, an ASCII string is valid utf-8, so when using hxs_utf8 on an hxcpp string which is ASCII encoded, it just returns a pointer to the ASCII...

No worries, it's worth making the distinction :)

There are a few more places where wstrings are converted to utf8 still. These include most of the system functions, though these are windows only, where wchar is equal to...

On Apple Silicon it still builds the x86_64 ndll by default unless `-DHXCPP_ARM64` is specified. Perhaps something needs to be updated in: https://github.com/openfl/lime/blob/8.2.0-Dev/project/Build.xml

With 55ca39da44a9f399b8aeff6d947be1e732ebd875, it would be good to double check that the pixman/openal changes here won't break anything for raspberry pi. > I realized that hxp's System.hostArchitecture doesn't have an ARM64...