Skip to main content

Dart 1.23: Better strong mode support

Dart 1.23 is now available. It introduces support for overriding fields in strong mode and a lot of other improvements. Get it now!

Screen Shot 2017-04-21 at 16.15.20.png
Figure 1: Overriding fields in strong mode

We have been spending a lot of our time on our unified front-end (explained by Vyacheslav Egorov in this short talk from the Dart Developer Summit). We're also doing a lot of work to support our critical customers (for example, Flutter gets better Windows support with this release) and solidifying strong mode.

Some notable changes in this release:
  • Overriding fields is now supported in strong mode. You don’t need to tag them with @virtual anymore.
  • Strong mode inference error messages are more helpful.
  • Strong mode now prefers the expected type to infer generic types, functions, and methods.
  • The UriData.parse method now normalizes and validates its input better.
  • Importing dart:io is now allowed in the browser, as a stopgap measure to make it easier to write libraries that share code between platforms (like package http that needs to run in the browser, on mobile, and on the command line).
  • pub publish now warns you when you’re importing a package that is not a direct dependency in pubspec.yaml.
  • pub get/upgrade now produces a more informative error message for Flutter.
  • dartfmt now makes precedence of cascades more visible, and adds other small formatting tweaks.
  • Fixes for Unicode character printing in the Windows console, inconsistencies between dartanalyzer and the analysis server in finding the options file, pub “UID too large” errors on OS X, and more.
For more information, see the changelog.

Please download the latest release and let us know what you think!

Popular posts from this blog

Dart in 2016: The fastest growing programming language at Google, 2nd fastest growing in TIOBE Index

Dart was the fastest growing programming language at Google in 2016 with millions of lines of code written. It also made it to TIOBE Index Top 20 this month (see TIOBE's methodology).

It takes time to build something as ambitious as Dart and, in some ways, Dart is still in its infancy. But we're glad the hard work is starting to pay off.

Many thanks to our amazing community!

We're going to celebrate by ... releasing 1.22 next week (as per our usual 6 week release schedule).

A stronger Dart for everyone

We are constantly asking ourselves:
How do we make developers even more productive when writing Dart apps? We believe that a critical part of the answer to this question is to make strongmode – a sound static type system for Dart – the standard for all Dart developers.

Teams that use Dart to build apps like Soundtrap, AdWords, AdSense, and Greentea say they really enjoy using strong mode features, such as early error detection. In fact, teams that have switched completely to strong mode cite not only early error detection but also better code readability and maintainability as major benefits. We hear this both from small teams and Рeven more so Рfrom large teams with hundreds of developers writing and maintaining millions of lines of Dart code. As Björn Sperber from Soundtrap says,
Strong mode and the smooth integration with IntelliJ is a joy to use and a huge improvement. If you’ve tried out Flutter, you’ve already used strong mode checks from the Dart analyzer.

Given the benefits …

AngularDart 3.0: Easy upgrade, better performance

AngularDart 3.0 is now available. It brings better performance and smaller generated code, while also making you more productive.


Version 3.0 is an evolution: although it has some breaking changes (detailed below), it is a smooth upgrade due to minimal public API adjustments. Most of the progress is under the hood—in code quality, stability, generated code size, performance, and developer experience.

Code quality:
2731 instances of making the framework code more type safe (using sound Dart).The AngularDart framework code size is down by 12%.Many additional style updates to the codebase:Changed to use idiomatic <T> for generic methods.Removed NgZoneImpl, all the code exists in NgZone now.Stability:
Many CSS encapsulation fixes due to update with csslib package.Fixed bugs with IE11.

Performance:
For the Mail sample app, we see 30% faster time-to-interactive (currently 3812 ms on a simulated 3G connection, measured via Lighthouse).Our large app benchmark shows 2x faster render times of…