Bob Nystrom

Re-opening because I missed your last example which is a really interesting one: > Example: > > ```dart > class A { > final bool value; > A(this.value); > }...

I would love love love to see data (especially from google3) on this if you have the time to dig it up.

The initial issue is a little vague and the subsequent discussion meanders (in part because of my mis-understanding of Leaf's issue and comments) but I believe the core issue is...

Interesting idea! > What if instead the default is that macros do not see the output of other macros at all I think that's the wrong default when it comes...

With the language as it is today, I think Lasse's suggestion is about the best you can do. If a bare callback function feels a little too raw for your,...

> * it implies you can actually extend a mixin, further complicating the user's understanding of mixins This depends a little on what you mean by "extend". When you have...

> But the point is new users would be using `extends ChangeNotifier`, instead of `with ChangeNotifier`, so they can't extend both `ChangeNotifier` and `DataModel` unless they learned to use `with`....

> `ChangeNotifier` is two steps down an inheritance hierarchy. I don't think it makes sense for it to be a mixin. I'm a little confused. The [docs](https://api.flutter.dev/flutter/foundation/ChangeNotifier-class.html) don't show it...

> Sorry I was thinking ValueNotifier, ChangeNotifier is just one step down. The inheritance hierarchy is: > > ``` > Listenable > | > ChangeNotifier > | > ValueNotifier >...

> > 1. It's a source of confusion for library consumers and a maintenance burden for library authors that _any_ class can be used a mixin if it happens to...