Closed dsnopek closed 1 week ago
If I understand it correctly, the handled failure case here would be a developer error. I would argue instead of silently failing, we should check for argument congruity before the loop and hard-fail on problems instead. Or at least, log an error if a problem is detected.
Discussed at the GDExtension meeting: we agreed on adding a warning if the argument and argument metadata count don't match.
Added a warning as discussed at the meeting
Fixes https://github.com/godotengine/godot-cpp/issues/1580
However, this shouldn't ever happen, if developers use the
GDVIRTUAL*()
macros, which will always call this with arguments metadata of the correct size.