language VS freezed

A future version of Dart will probably support macros which should make this all a bit easier to use, similar to how Swift 5.9 works which makes already fantastic use of its new macro capabilities by integrating mobx (or solidjs) like reactivity into SwiftUI by a harmlessly looking @Obervable annotation.

Yes, that needs a bit of boilerplate for the constructor declaration and the extra build method, but I personally don't mind and with implicit constructors this will become much easier. Also, you get a performant UI as Flutter knows to not redraw widgets that didn't change.

I implemented a prototype version of the algorithm in that paper when exploring exhaustiveness checking for pattern matching in Dart.

I found it pretty easy to understand, but also really easy to get it to generate huge combinatorially large spaces. Some careful memoization and deduplication helped, but even so I never got the performance to a state I considered acceptable.

Instead, I went with Luc Maranget's classic approach and figured out a way to adapt it to a language with subtyping (with a ton of work from Johnni Winther to figure out all of the hard complex cases around generics):

https://github.com/dart-lang/language/blob/main/accepted/fut...

The performance (in the prototype!) was dramatically better. You can always make pattern matching go combinatorial, but I haven't seen any real-world switches get particularly slow with our approach yet, and we have some fairly large tests of matching on tuples of enums.

We are working on a proposal to add macros to the language for sophisticated compile-time metaprogramming. But the goal is more for larger-scale uses of metaprogramming—synthesizing entire new declarations—and not really about extending the syntax.

Looked at, never gonna happen (says https://github.com/dart-lang/language/issues/69). The language would have to have been designed for that from the beginning, and now there are too many constructs that would require too much "guessing" to get proper syntax right.

However, I'm super stoked to see the community pushing forward. I think when/if metaprogramming becomes available (https://github.com/dart-lang/language/issues/1482), similar magical experience would be possible in Dart everywhere. Consider following that issue and providing feedback. IIRC the champion of that feature (https://github.com/jakemac53) would like to make DI frameworks one of the key use-cases for the language feature, and will appreciate your thoughts on what primitives you'd need.

Dart is openly developed. If you want to know what Dart 4.0 will bring browse the Github (https://github.com/dart-lang/language).

Macros: https://github.com/dart-lang/language/issues/1482

Not sharing memory between threads was a deliberate choice and I think it saves us from a lot of bugs. Especially race conditions in multi threaded code can be a pain to debug. But more you read a long discussion here: https://github.com/dart-lang/language/issues/333

Specifically, see column 3 "being implemented" at https://github.com/dart-lang/language/projects/1 which links to specifications of in-progress new Dart features.

The official site does show what you can use it for but to explain a bit more, it helps you work faster.

One rather minor suggestion: it took me a while to understand exactly what the benefits were, but the example shown on this page of the docs summarized it well. I would suggest showing an example like that at the top of the main Readme and first page of the site, before or right after the motivation section, similar to how Freezed immediately shows its value proposition.

Read more on what you can do with Freezed.

Once the package has been created, we will install freezed for JSON serialization and value equality , as this library provides helpful tools for these tasks. We will use json_serializable for JSON serialization. To install freezed and freezed_annotation, open your terminal inside the models package and use the command:

Data class: freezed

I'm all in on flutter_bloc (cubit actually), freezed, go_router & supabase_flutter.

What were your problems with it? I found it to be basically typescript, but without javascript's awful baggage and no union types, which is fixable with https://pub.dev/packages/freezed

It uses the mechanism of the freezed library to automatically generate model objects based on JSON files.

Freeze --> Model Mapper