Rewriting freezed with Macros | Observable Flutter #47
HTML-код
- Опубликовано: 10 июл 2024
- Watch as Craig Labenz and Rémi Rousselet discuss Rémi's experience rewriting his infamous data class package, `freezed`, with Macros.
The latest from Flutter → goo.gle/flutter-latest
Watch more Observable Flutter → goo.gle/ObservableFlutter
Subscribe to Flutter → goo.gle/FlutterYT
#ObservableFlutter #Flutter
Speaker: Craig Labenz
Products Mentioned: Flutter 
Наука
Any talk with Rémi Rousselet is worth a watch, thank you!
Thanks for the curated/edited closed captioning - much appreciated
It was soo fun to watch and code along!! Thanks Craig and Remi!!!
Rémi Rousselet is Genius man❤
Your t-shirt has a keyed out flutter logo.
What? Is He a Terminator😅
Great video 💪
Such a great content here on Observable series!! Thanks for that.
Could you increase the video quality? It looks like watching a 720p video even when watching at 1080p.
"please, give a forecast when the macros will be in the stable"
"29:08 sadly the forecast that I can give is that there is no forecast."
but I can live with one of the reason that Devtools not hooked in yet
i need help , i just want to know how can we set global configuration for macro. is that from analysis_options yaml or any other logic , consider we have a macro package for Equatable , here we want EquatableConfig stringify to a bool that is non-final at analysis time as well as runtime is there any way to assign Such Global config
We'll actually get working (usable because of the speed) function widgets instead of class based widgets
I'm afraid there is too much emphasis on macros and that people will start writing macros for things where it isn't a good fit. Debugging errors originiating from inside macros have been a pain in other languages, and I can only imagine the confusing errors we will start getting when people start using macros. Most of the discussions seems to be on `writing` but very little has been said about how troubleshooting, debugging and errors would look.
did you not see the part of the talk on diagnostics? IMO diagnostics / exception throwing is one of the best things that Dart's macros got right (for now, at least). you can throw exceptions not just on the macro, but on the given arguments of the macro, the class or method its applied to, or really any code that may better explain the issue to a developer.
Tbh I would wait to see what the macros implementation looks like before worrying about it being an overused feature.
Can't get behind the fact that the dart team named the class property *clazz* because class is a reserved word lol😂
Hello Flutter
Will Riverpod change?
😮
"something no language has ever done" uhh... Rust macros? So so many languages that have macros?
I think augmentstiond are possible different
I think Craig meant that dart's macros are generated "on fly" while in other languages (like in Rust) they're done at compile time
darts macro are generated on the fly by the dart analyser server afaik. rust also does that
@@gorudonu I concur, they weren't specific on that point but that's definitely what they meant since other languages with macros exist. With Dart you will be getting feedback in real-time when you are using the macro feature which is quite unique in of itself.