warning 229 when view "enum struct" as an array

[Localia-cn]

Compiler version: 1.12.0.7134

A warning will be prompted when using view_as to convert an enum struct to an array type other than any[].

enum struct TestStruct
{
	float x;
	float y;
	float z;
}

void FuncFloat(const float input[3], float output[3])
{
	output = input;
}

void FuncAny(const any input[3], any output[3])
{
	output = input;
}

public void OnPluginStart()
{
	TestStruct v1;

	float vec[3];
	vec = view_as<float>(v1); // warning 229: index tag mismatch (symbol "v1")

	FuncFloat(view_as<float>(v1), view_as<float>(v1));	  // warning 229: index tag mismatch (symbol "v1")
	FuncAny(view_as<float>(v1), view_as<float>(v1));	  // this is no problem
}

[dvander]

Enum structs can only be converted to "any[]". We could consider a rule where if the inner types are all the same, this kind of conversion would work. But it's a bit esoteric so I'd rather gauge interest/usefulness.

[Localia-cn]

Enum structs can only be converted to "any[]". We could consider a rule where if the inner types are all the same, this kind of conversion would work. But it's a bit esoteric so I'd rather gauge interest/usefulness.

How about only checking if the sizes of enum struct and array are equal? Similar to allowing the conversion between int[4] and float[4]. The purpose of using view_as is inherently to convert one type to another, as seen in the common conversion between int and Handle types in Sourcemod plugins. Those who use view_as should be aware of what they are doing, and converting to seemingly mismatched variable types should not be a concern.

If such conversions are allowed, people can define their own Vector3 type and directly intermix it with functions in Sourcemod that use float[3] as parameters. Angle, Vector, and Point will have clearer distinctions, and their methods can be isolated through enum structs, which is very helpful for improving the readability of some complex mathematical computation code.