Skip to main content

Enums and Async primitives in Dart

Support for enums, async, and deferred loading are now officially part of the 2nd revision of the Ecma-408 standard, the Dart Programming Language Specification. The second revision was approved last week at the Ecma General Assembly.


You can find more information about using the new features in our language tour on dartlang.org:

Enums

Enums help developers express clear intent with minimal code, and help tools catch potential bugs. Here is an example of an enumeration of form states:

    enum FormState { OPEN, INPROGRESS, CLOSED }

Tools can even warn developers if they omit an enum value from a switch statement, which helps identify potential bugs.



Async

Dart has always had strong support for asynchronous programming, with core library features such as Future and Stream. Now, with the new language primitives async and await, asynchronous code is much easier to read and write.

The following code is easy to read, because a developer can follow the logic, line by line. However, the lookUpVersion() function actually runs asynchronously!

checkVersion() async {
  var version = await lookUpVersion();
  if (version == expectedVersion) {
    // Do something.
  } else {
    // Do something else.
  }
}

Deferred loading

Users expect web applications to load extremely quickly. Dart's new deferred loading syntax helps a developer send minimal code to the client on the initial download, and load extra functionality on demand. This means that the user downloads only the code that they need to get started, resulting in faster load times.

Enjoy!

We are excited about these new language features and are working hard to provide full-fledged implementations of the new features in the Dart SDK as soon as possible. We look forward to your feedback on the new features.

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…