Skip to main content

Dart Language progress update

Posted by Gilad Bracha


The Dart language team gathered to discuss some of the open issues with the language.


Language Bugs: Will review language bugs and either fix, mark as deferred to future release (meaning no decision but distinctly possible in the future) or close. 30 bugs already processed last week.

Cascades: The new dart2js compiler has implemented the spec. We will review to see if spec needs minor adjustments in light of implementation experience. We don’t expect any significant changes.

Defaults in interfaces:  We expect to support these. Intended semantics are to give a warning if violated by implementor. However, if no default is given in the interface we will not interpret that as a default of null.  People can override in the default code if they want to, and may have reason to.  In any case we have no way force them to do otherwise. We will pin down draft specification.

Generics reification: We discussed whether to back off of that. The decision is to retain reification unless major problems arise in dart2js. We do not anticipate such problems, but once dart2js implements the semantics we can quantify any costs.

Multiple initialization points for finals:  Tendency is to keep current spec and fix implementation, but we do need to see what impact it has on code base. Ongoing discussion.

Repeated keys in map literals: We noted that we could disallow this if the keys are strings constants, but since we are hoping to generalize that, it might not make any sense.

Switch statement: Decision is to restrict switch to operate on compile time constants of uniform type - either int or String. We could extend this to enums if we ever add them. The motivation is that switch is only useful as a highly optimized jump table, and so we should focus on that; otherwise use if-else, it’s clearer. We will adjust spec accordingly.

Popular posts from this blog

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…

Dart 1.24: Faster edit-refresh cycle on the web & new function type syntax

Dart 1.24 is now available. It includes the Dart Development Compiler and supports a new generic function type syntax. Get it now!


Figure 1: DDC debugging in Chrome.

Some notable changes in this release:
pub serve now has support for the Dart Development Compiler. Unlike dart2js, this new compiler is modular, which allows pub to do incremental re-builds for pub serve.In practice what that means is you can edit your Dart files, refresh in Chrome (or other supported browsers), and see your edits almost immediately. This is because pub is only recompiling your package, not all packages that you depend on.There is one caveat with the new compiler, which is that your package and your dependencies must all be strong mode clean.You can also use the new compiler to run your tests in Chrome much more quickly than you can with dart2js.Read more in the changelog.You can now publish packages that depend on the Flutter SDK to pub. Moreover, pub.dartlang.org has started tagging Flutter plugins with …