Array cannot be Un-Typed, or Array.is_typed() is broken.

[rambda]

Godot version

4.0.beta.16

System information

N/A

Issue description

var typed_array: Array[Node] = []
var array : Array = typed_array
print(array.is_typed())
print((typed_array as Array).is_typed())
var array2 : Array[Variant] = typed_array
print(array2.is_typed())
print((typed_array as Array[Variant]).is_typed())

All prints true

Steps to reproduce

N/A

Minimal reproduction project

godot.4.0.beta15.bugs.0.zip

[anvilfolk]

This may have changed with the big #69248 PR of @vonagam's. Would you be able to check in Beta 17?

[vonagam]

Well, the code that shown would not change. But there is a way to make array untyped now:

var array: Array = []
array.assign(typed_array)

[dalexeev]

I checked the description and MRP (please don't combine many issues in one MRP) and I don't think there are any bugs/issues that are currently unresolved or not tracked in other threads.

Since arrays are passed by reference, it makes no sense to make an already existing array untyped, which would break the following code:

var a: Array[int] = []
var b = a
b.set_untyped()
b.append("string") # Now `a` contains string?!

Instead, you should create a new array. Note that var array : Array = typed_array does not create a new array. But you can use the assign() method, which assigns (copies) the contents rather than a reference.

See also:

• GDScript reference - Typed arrays
• Functions accept typed arrays and cannot inherit conversions #80586
• Behavior of typed arrays godot-proposals#7364
• Add typed array conversion constructor #71336

Note that there are bugs that may cause this to work incorrectly in some cases:

• GDScript: Fix typed array hash #72514 (comment)
• GDScript: Don't make array literal typed in weak type context #81332

If you still have any issues with typed arrays, please post here, in the appropriate thread from the list above, or open a new issue.

Thanks for the contribution nonetheless!