Skip to main content

Notes from October 8 language design meeting

Dart engineer Bob Nystrom has posted the notes from the October 8 language design meeting. He writes:

Making throw an expression

Lars wondered what the motivation behind adding to the spec was. My recollection was that it was so you could use it in lambda-body methods:

  class ImmutableList implements List {
    void add(item) => throw new NotSupportedException();

Kasper looked at the code to parse throw as an expression and found out it's hideous because of rethrows.

Lars wants to know more about the impact of this. How tightly does it bind when embedded in an expression? Do we want to allow it in a ternary operator? He wants to know more about the original motivation behind this.


Lars suggested we could do the general purpose solution and allow constructors but he would prefer something stepwise where we don't allow constructors at first. You could still have fields but they would need initializers at the declaration. We can get some experience with the feature and this will probably solve more use cases.

Gilad is all for it and asked about the timeline.

I asked if we'd be able to make changes to corelib to take advantage of mixins once they are supported even if those happen to be breaking changes. The answer is yes, but we of course want to minimize breakage.

Library tags

I asked about the intent behind library tags. I thought you only needed them if you use part, but the spec says the only place you can omit them is scripts which have a main() method.

Kasper says we want to encourage people to name their libraries because you get nice benefits like it can tell you if you accidentally import the same library from two different paths, which would be confusing because you'll get two copies of your statics.

Right now, the spec is maybe stricter than our original intent, but its easier to loosen it over time than go the other way, so lets leave it as it is.


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 2.1 and new Components

AngularDart got its own dedicated team 5 months ago. Last month, we launched 2.0 final on the Dart Developer Summit. Today, we’re releasing the first minor release after that: 2.1.

Since the focus of AngularDart is Productivity, Performance, Stability, there are no major breaking changes (see the changelog) — but a lot of behind-the-scenes improvements. Your apps will get slightly smaller and faster (even relative to 2.0 which already made huge strides in size and performance since the compiled-from-TypeScript days).

Many features that AngularJS had to implement for JavaScript and TypeScript are not needed in Dart (because Dart already has those features out-of-the-box). So we’re removing them from AngularDart. Renderer is deprecated in favor of plain-old dart:html. NgPlural is going away — Dart programs can use the package:intl library.

New components

On the Dart Developer Summit, we launched AngularDart Components — the material design widgets Google is using in customer-facing apps …