gcb
Reputation: 14550
Understanding @mustCallSuper
The docs says implementations must call super. And there are even questions about where to.
But I boldly did not call it on an annotated method (State.initState) I overrode (on flutter's State) and everything compiled and worked without any problem.
So, Is this implied by the compiler (or flutter tooling?) and super was called behind my back? Or does the static analyzer doesn't know how to enforce this?
Upvotes: 0
Views: 317
Answers (0)
Related Questions
- Flutter App stuck in emulator at "Waiting for VM Service port to be available..."
- Shared_preferences on iOS throws PlatformException(channel-error, Unable to establish connection on channel., null, null)
- How to create a shared library in android and use it in flutter?
- Understanding Factory constructor code example - Dart
- Flutter 2.0.2 Null check operator used on a null value
- Error: Could not find the correct Provider <List<Auftrag>> above this Widget
- Does Dart have an equivalent of TypeScript's --noImplicitAny, enforcing static typing unless explicitly disabled?
- What's the design benefit of Flutter's (Widget)State/StatefulWidget pattern?