This is just a meta issue to track overall progress and bugs tied to pushing optional new and const in Dart & Flutter.
- [Optional new and const crash during compilation on Flutter 0.2.7-pre.6]
(#32737) - [Finish implementation of optional new and const] (#32729) – moved to 32737
- [Dart compiler exception with Flutter master] (#32729) – moved to 32737
- Optional new combined with generic constructor fails (#32802) – duplicate of 30922
- [Front-end handling of optional
new
andconst
.] (#30922) - [Test Analyzer optional new/const on large code bases] (#32821)
- [Test CFE optional new/const on large code bases] (#32820)
- [Disable automatic const insertion in analyzer] (#32819)
@eernstg In all likelihood for Flutter at least we’d probably just create special non-const constructors for those rare cases where calling “new” instead of “const” makes sense.
@a14n Yeah that seems good.