This new release brings several important bug fixes to problems that could cause crashes and other unexpected behaviours in some situations. It's highly recommended that the upgrade is made as soon as possible.

Besides the bug fixes this version also brings support for multiple subtypes in templates (Thanks Amer Koleci), support for native calling conventions with Linux and arm processors (Thanks Carlos Luna), and support for octal and binary literals (Thanks ketmar).

The script compiler has been enhanced to finally support implicit conversion from primitive types to registered value types by allowing the compiler to call the appropriate constructor. This has been a frequent request from users.

Regards,

Andreas

Now we just need to find the question :)

Hmm. This currently doesn't work because the compiler would first implicitly convert 42 into an instance of any, and then assign that instance of any to the declared variable. It won't initialize the declared variable directly with the constructor that takes uint. If you add an opAssign that takes an 'any' it should work though.

Quite frankly, I think this is a 'border case'. I mean, the use of copy constructor, or in this case the constructor that takes an uint to initialize the variable would just be an optimization that the compiler could make. Since the any type doesn't have the assignment operator it probably shouldn't be allowed to be initialized with this syntax.

I didn't add a lot of new tests for this change, because the code mostly already existed. I mostly only enabled the path to allow implicit cast from primitive to value type. All the rest of the logic for when and where implicit casts are used is still the same.

Way back when I implemented CScriptAny, I decided to make the object a reference type, allow a handle to it be passed around.

It would definitely be possible to implement the type as a value type too, but then when passing the type around it would have to be as copies which would be more expensive.

The problem is not the container itself, but what it contains. If it holds a value type, then that value needs to be copied together with the container, if it holds a reference type, then that reference needs to be increased, and so on.

But, by all means, do the benchmark. I'd love to be proven wrong :)