Script using enum array fails to compile after upgrading to 2.39 WIP

[HenryAWE]

Found by a test case of asbind20.
Script segment:

my_enum[] arr(n: 2);
assert(arr.size == 2);
assert(arr[0] == my_enum::zero);
assert(arr[1] == my_enum::zero);

The message callback says:

ERROR (factory_size_enum:3:15): No conversion from 'my_enum' to 'int64' available.
ERROR (factory_size_enum:4:15): No conversion from 'my_enum' to 'int64' available.

The test suites of asbind20 are using its own array implementation, here are the declarations of related interfaces:

array<T> //array type registered to the script engine

// opIndex declarations
T& opIndex(int)
const T& opIndex(int) const

// enum in C++
// registered by RegisterEnumValue
enum my_enum
{
    neg_one = -1,
    zero = 0,
    one = 1
}

The above example is using code from the newest commit of AngelScript.
This script compiles & runs as expected using AS 2.38 & 2.37.

[anjo76]

Thanks for the report. I'll investigate this.

[anjo76]

I have not been able to reproduce this.

Here's what I've tried:

static bool TestEnum()
{
	asIScriptEngine   *engine;
	COutStream         out;
	CBufferedOutStream bout;
	int                r;
	bool               fail = false;
        
	// Test enum conversion to int64
	// https://github.com/anjo76/angelscript/issues/84
	{
		engine = asCreateScriptEngine();
		r = engine->SetMessageCallback(asMETHOD(CBufferedOutStream, Callback), &bout, asCALL_THISCALL);
		bout.buffer = "";

		engine->RegisterEnum("my_enum");
		engine->RegisterEnumValue("my_enum", "zero", 0);

		RegisterScriptArray(engine, true);
		engine->RegisterGlobalFunction("void assert(bool)", asFUNCTION(Assert), asCALL_GENERIC);

		r = ExecuteString(engine, "my_enum[] arr(1); \n"
								  "arr[0] = zero; \n"
								  "assert( arr[0] == my_enum::zero ); \n");

		if( r != asEXECUTION_FINISHED )
			TEST_FAILED;

		engine->ShutDownAndRelease();

		if (bout.buffer != "")
		{
			PRINTF("%s", bout.buffer.c_str());
			TEST_FAILED;
		}
	}

@HenryAWE can you see what you're doing differently? Perhaps you're setting some engine properties to non-default values?