Variable haxe.ds.Vector type unable to be used or initialized, returns "unknown variable" error.

[BeastTornado]

When initializing a Vector variable, whether using a simple "Vector" or a specified reference "haxe.ds.Vector", an "unknown variable" error is returned. My assumption is it is an issue with Abstract types, as maps can have the same issue when referred to with a path reference (ex: "haxe.ds.StringMap".

[BeastTornado]

Ok nvm maps also just genuinely don't work at all either

[Jamextreme140]

Vector is a full abstract type, because it creates a native fixed-length array depending of the target (ex. Vector in C++ uses cpp.NativeArray)

On the other hand, I will check about the map thing since StringMap is a class and it should not fail. However, for now I recommend to initialize any map like this:

var map:Map<String, Dynamic> = ["" => null];

This will create a StringMap based on the key type

[Jamextreme140]

Which version of Codename are you using? Legacy or Latest?

[BeastTornado]

Latest

[BeastTornado]

When initializing the map in the way you had shown, the game crashed.

[Jamextreme140]

Ok. Try importing the StringMap class first and then create it.

import haxe.ds.StringMap;

var redRings:StringMap<Dynamic> = new StringMap<Dynamic>() ;

I have used the class and it works fine for me.

[Jamextreme140]

Once I'm available, I'll check the class path reference thing, ok?

[BeastTornado]

When importing the StringMap class I am getting a null function pointer error when attempting to call map functions off of the variable after initialization.

[BeastTornado]

For reference, this is how it is initialized:

[Jamextreme140]

Latest

Latest GitHub Actions Build or v1.0.1?

[Jamextreme140]

I just did some tests, and I fixed the path reference thing. But the StringMap usage works fine for me, and the previous example should work

[BeastTornado]

v1.0.1

[Jamextreme140]

I see why. Most of the current fixes on HScript has been fixed after V1.0.1, like an issue with using feature and more.

I recommend to use the latest GitHub Actions Builds or avoid the using until the next version

[BeastTornado]

I'm still having the same issues on the newest GitHub Actions Build, no differences