Cedric Hippmann

Yeah i see these points and agree. Let the property ordering do it's job then.

Yeah. I'm unsure what to do here; - either we implicitly register these collections as a VariantArray under the hood -> imposes performance problems as lists need to be converted...

What about both? As a quick fix we implement the first variant. And later on we can implement the more complex and performant variant? Fixing the leaks would be nice...

@AutonomicPerfectionist no not yet. Neither of us got around to do the necessary changes yet. I might have a look tomorrow. If not: adding the reflect dependency here should be...

> I wonder if runtime crash we had when testing with graalvm native-image on iOS is not linked to this issue. > > We had `Unreacheable code` when calling ::class,...

Probably no longer necessary after the merge of https://github.com/utopia-rise/godot-kotlin-jvm/pull/437. Still we need to look into this as the signal parameter names are still extracted with PSI. But they are at...

Hey @marcopennekamp Thanks a lot for the quick sum up. I think we're then no longer really affected by this change in regard to our symbol processor. There since #437...

@piiertho Isn't this resolved now after switching to godot actions for building the editor?

Quick update on this: Now that #433 is merged and once #441 is merged, we can finally support java out of the box (as our symbol processor, which is based...

TLDR; I'm one of the maintainers who's strongly in favor of explicit registration. However I do see I'm definitely the minority and i do see the painpoints. Some things need...