Danil Alexeev

~~This makes sense since `BUILTIN` types cannot accept `null` value and there is no `Nil` type in GDScript. But in my opinion, this should be fixed first in the analyzer...

> There is no other type other than `Variant::NIL` that can represent `null` Sorry, I was thinking that we could use `Variant::OBJECT`, but I forgot that it is also not...

I'm guessing this is because the inspector and debugger use `SpinBox` to display `float`s. `SpinBox` inherits `Range`, which doesn't allow you to set non-finite values. So we should probably either...

> There are some weird errors on the CI tests though, not sure what's going on. * See #91120.

To fix #74686 and #91155 I added the following: ```diff @@ -2998,11 +2998,10 @@ Variant GDScriptFunction::call(GDScriptInstance *p_instance, const Variant **p_a VariantInternal::initialize(&vref, Variant::ARRAY); *VariantInternal::get_array(&vref) = ref; - Variant **args = instruction_args;...

I think the old behavior is also incorrect, non-static members should not be accessible in a static context, there should be an analyzer error. If you try to call `not_static()`...

> Looking at the changelog, I suppose this might have been caused by #90223 ? Yes, most likely. But I think this is a valid assumption for the compiler, we...

Can `script_backtrace()` return data in a structured form (`Array[Dictionary]`), like [`get_stack()`](https://docs.godotengine.org/en/stable/classes/class_%40gdscript.html#class-gdscript-method-get-stack)? It also looks like this PR will resolve godotengine/godot-proposals#105.

I think this is too specific a warning. Instead, we could add something like `IMPLICIT_CONVERSION_CAUSES_COPYING`. Since this can potentially happen not only with arrays. And also such implicit conversions occur...

* See also #33080. I wanted to salvage/re-implement it. I think this should work like `Dictionary` key/value editor, the user could select the type first, then the value.