-
Notifications
You must be signed in to change notification settings - Fork 9.8k
Conversation
Hm, this is sad. That class was meant to be usable as a superclass too. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I'm going to submit this PR because it's non-breaking but will unblock the move to |
I filed dart-lang/language#31 for discussion. |
I really would rather we didn't do this. |
Why not? |
(I'm assuming you are referring to this PR and not flutter/flutter#22290 or dart-lang/language#31) |
Because it's ugly. :-) We have an ordinary class, and we want to use it as an ordinary superclass... why would we want to use it as a mixin in this case? WidgetsBindingObserver was intended to be a regular class that in some more advanced cases might be used as a mixin or an interface, something that Dart supports out of the box and is idiomatic. Why would we shy away from that? |
I think dart-lang/language#31 (comment) would solve this issue if accepted. |
This reverts commit c8e1166.
This change is fully backwards-compatible. The reason I'm doing it is that Flutter is converting to the new
mixin
syntax, which forbids extending mixins.See also: flutter/flutter#22290