Skip to main content

Notes from 5/28 Dart Language design meeting

Posted by Bob Nystrom

Sorry for the long delay. This meeting was just skimming over a bunch of issues in the bug tracker, so forgive me if there isn't a lot of context here.

Import syntax

Kasper and Ivan did the original syntax design. If we want to iterate on that, we should get them in a room.

Catch syntax

Looks weird because it's more like a variable declaration than a parameter declaration. Gilad says we'll figure it out soon and should be a minor change.

Statics in interfaces

Kasper: People find default classes hard to follow. We could consider allowing simple redirect code for constructors in interfaces.

Instance field should be allowed in initializer expression when it is initialized via "this.foo" sugar.

Bug 3263. Gilad says: if the sugar doesn't do what you want, don't use the sugar.

Private names

Dart uses isolates for security, so we don't feel pressure to have JS-private-names-style security.

The default implementation of an interface must not over-specify generic paramaters

Bug 3279. We're OK with the current semantics.

Abstract or static method named the same as enclosing class

Bug 3284

Kasper: The VM is slightly broken with respect to reporting. We should clarify the spec.
Lars: It is very confusing.
Gilad: That's why shadowing is a warning.
Kasper: Should say that if it's the same name, it must be a constructor. If it has a return type or abstract, that's an error.

Function expression vs statements

Can we get rid of return types and/or names?

Bob: Idiomatic dart doesn't have return types or names for function expressions. The style guide may discourage it soon. [ed: it does now.]
Kasper: Getting rid of return type for function expression gets rid of the nasty infinite lookahead with generic return types.
Gilad: What about contexts where you can't distinguish between expr or stmt?
Kasper: If it has a return type or a name, it's a statement. Done. It must be in statement position.
Gilad: Let me try to come up with some rules for it to see if it hangs together.

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 …