Timothé Larivière

Let's keep it for a later release. @edgarfgp added the possibility to pass directly a `Xamarin.Forms.Style`, so should be good enough for now.

Other features like `ViewRef`, Style widgets, perf optimizations will wait for a later time. The current goal is to release a (minimal) working version publicly so people can try it...

Moving #27 and #26 out of release 1 #27 is not really mandatory for the first release. All other frameworks (Elm, React, SwiftUI, etc.) only apply this optimization on repeated...

Yes. It's a good idea. Might require a bunch of code to add though.

I don't think there's anything preventing us from doing so 


Like pretty much all other frameworks (React, SwiftUI, Flutter?), we have the concept of key at the widget level. This allows the diffing algorithm to match 2 widgets between 2...

This is also crucial for virtualized list I believe

Not as efficient, but what would it mean to make it `u16 voption` instead? I guess we can go with numeric for now, the string was mostly for conveniency. But...

@twop In the end, I implemented virtualized collection without needing diffing so keys are not necessary. But it would definitely be improving performance in layout controls