João Pedro Braz
João Pedro Braz
@anvilfolk Forgot to address the `if x: # Cannot distinguish between x == "" or x == null` but I think that's a no brainer, if the user cares for...
> GDEXTENSION_VARIANT_OP_IN, @AThousandShips I knew I was missing something, even asked on #gdextension, thank you!
@AThousandShips Weird thing is, I think I did that already:  https://github.com/godotengine/godot/pull/76843/files#diff-29b903ebcf0b26a6b2fa3e617462e06b69b6d5201e1dda76095076949da8a0f8R139
> > Oh sorry missed that, now that you mention it I did see it, then this must be due to lack of sync in godot-cpp, got myself confused looking...
Indeed... @akien-mga is this something you've encountered before?
Looking at how the godot-cpp test is executed I think I really need to get the new operator merged upstream on godot-cpp before this PR can be merged: ```yml #...
> The PR description doesn't make it clear to me whether the behavior of Object types got changed (which would be a breaking compat change, but maybe one worth doing)....
A topic @dsnopek brought to my attention over #gdextension on RocketChat is that it might be necessary to add the new Coalesce Operator as a method of Variant itself. Could...
> > Looking at how the godot-cpp test is executed I think I really need to get the new operator merged upstream on godot-cpp before this PR can be merged:...
> Where the PR would truly shine is with dictionaries. `dict_1?.dict_2?.dict_3?.value` > > Unfortunately, `dict_1.dict_2` triggers an error if the key `dict_2` doesn't exist in `dict_1`. This is counter intuitive...