Marc Rousavy
Marc Rousavy
It works!!! 🥳 
So now it works (finally! 🥳), but the performance improvements are in the 5%-10% area, which is less than I hoped for. We can still optimize a few things like...
Strings in Kotlin got a bit faster though: 
The performance improvements are much less than what I originally anticipated. It seems like Nitro was already really fast on Android. Going directly to JNI didn't really give any benefits...
JFYI; this will not be supported. A struct cannot reference itself cyclically, not in C++, not in Swift. Unless you make it a pointer/heap-allocated, but I don't think we should...
To be fully honest, I have never trained my own models. I always used pre-trained models, so I don't really know how to answer your question, sorry.
> Anyway, is Hans pissed because I asked for Jäger instead of Wiener Schnitzel? He's not getting back to me and I feel its a personal thing? Maybe Hans already...
This is where we have this case already: Why didn't this `.value` access fail in Release mode before? [All release builds in CI went through just fine](https://github.com/mrousavy/nitro/actions/workflows/build-ios-release.yml). Maybe we need...
I just added a test for this that passes the following struct: ```ts interface PartialPerson { age?: number name?: string } ``` ..to native, and native Swift accesses `.age` and...