riverpod VS language

From a library standpoint, I would recommend https://riverpod.dev over any other state management libraries for productivity purposes.

I have the following code. When I hot reload I get an error like this. Apparently this is fixed in dart 3 and Remi mentions a solve here. I am unclear how to refactor my code to achieve the solve without upgrading Flutter to an unstable version (which I've tried and cannot use because of certain render issues).

I saw this official example but it doesn't use riverpod_generator : https://github.com/rrousselGit/riverpod/blob/master/examples/todos/lib/todo.dart

Looking at the riverpod.dev docs, I saw that they were using Docusaurus which led me to creating this site. You can think of it as a guide or your go-to when trying to build gRPC servers and clients using Dart. It's open source hosted at this repo and everyone is really invited to Collaborate.

Riverpod Docs

I think you might need to use a state management if you want to keep the username and email always in scope in your application. Consider using riverpod or provider

You're right, it's Riverpod.

Sources: Riverpod: https://riverpod.dev REST: https://github.com/codeReview-youtube/flutter_auth_api PROJECT: https://github.com/codeReview-youtube/flutter_rest_riverpod_authentication

I noticed that I can enable inline-class as an experiment to play with Extension Types. You need to also add sdk: ^3.3.0-0 to your pubspec.yaml.

Current syntax is not all that bad if you are going to do OO and add various helper methods on `Message` and its subclasses, but if you just want to define your data and no behavior / helpers - then it is exceedingly verbose.

[1]: https://github.com/dart-lang/language/issues/3021

Reference

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.

Coming from a Dart context here where that team is also looking at adding Macros to the language. It was really interesting to compare and contrast some of the approaches https://github.com/dart-lang/language/blob/main/working/macr...

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 know that it would be nice not to use the generator at all, but we have to wait until static metaprogramming is implemented in dart. https://github.com/dart-lang/language/issues/1482

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.