@ASalvadorini@AymenMak84548 I think most of the stuff in the linked issue has landed under experimental flag and we are in discussion to remove the flag...
though I am not sure how it helps in this particular case.
@AymenMak84548@ASalvadorini that's has not been the case for ~3 years now, since Dart 2.19 was released. If you are using compute / Isolate . run you can use arbitrary closure and send back almost arbitrary objects with few exceptions almost all of which have to do with FFI/native resources.
@jezell@viktorlidholt@puf Yeah, I have seen it before. We have considered this at various stages - but impossibility to make JS interop work normally makes this much less interesting then it could be.
Flutter in your pocket, on your web browser, and now... in your car 🛠️
See how Flutter is helping Toyota deliver an intuitive, smartphone-like experience to 2026 RAV4 drivers across the world.
@trolleybusass В Швеции нет штрафов за "unødig røg og støj"? Все эти специальные модификации обычно незаконны - и если полиция их видит, то вызывает на syn
@ppkatariya@dart_lang It can be (and it can be useful in Flutter as well, e.g. types like matrix and vector are better be value types) -there are various cases where it can be impactful, these are just relatively niche.
@ppkatariya@dart_lang Because widgets typically outlive the frame in which they are allocated. Stack alloc helps when object is allocated, passed down the call-tree but is no longer used after caller finishes. Value types help with small temporary/utility objects (like slices).
Among all the I/O news, I want to spotlight what I personally think will be a major moment in the evolution of Flutter: Our new project governance approach.
Details in 🧵
This is the greatest video I’ve ever seen. No notes. The lifeless clanker carcass just laying there. No crowd reaction, anything. Just Billie Jean. Until its lifeless shell is shamefully dragged off. Purely amazing.