Skip to main content

Rolling back setter syntax, more updates from Dart language design meeting

Posted by Bob Nystrom

Here's my notes from this Monday's Dart language design meeting.


New getter and setter syntax

We heard lots of feedback from users that they don't like the new setter syntax. Instead, we'll keep the current syntax, so no more "=" after the setter name. Instead, just:

    set blah(value) => ...

We will go ahead with the getter changes (removing ()).

Ryan Dahl's thread on misc

Go's syntax for loops and stuff versus Dart's is really just a matter of taste. Dart tries harder to be similar to other languages to make it easier for users to get comfortable and to make porting code easier.

We talked a bit about optional semicolons. There is some vague worry that we could end up with some of the problems that JavaScript has. For now, we don't have any plans to make them optional. But, since doing so wouldn't be a breaking change, we can always decide to do that later.

Lots of people don't like "&" for export. Message received: we'll do something different. Not sure what yet.

Parameter lists

We have a design for a modification to parameter lists that lets you define optional positional parameters that are not also named. Sometime soon, I'll see if I can get a document out that explains it.

We won't know how well this works until we port code to use it. We aren't sure how many of the current APIs are using optional parameters positionally or by name. So we'll try it out and see if we need to iterate on it again.

Cascades

Are implemented everywhere now (VM, dart2js, editor). Users can start playing with them!

Non-const statics

These are coming soon. This means you'll be able to initialize top-level final variables, and static final fields using non-const initializers. They will be lazily evaluated the first time the variable is accessed.

As always, thank you all very much for the constructive, detailed feedback. As you can see, it directly affects the course of the language. Dart wouldn't be what it is without you. We encourage you to join the conversation on the Dart mailing list and ask Dart questions on Stack Overflow.

Popular posts from this blog

AngularDart 4

AngularDart v4 is now available. We've been busy since the release angular2 v3.1.0 in May. Not only did we "drop the 2", but we also improved the compiler and tightened up the framework to give you smaller code, we updated the package structure to improve usability, and we added several new features. Check out the updated documentation to get started.
Just angular Upgrading to v4 will require more than updating your version constraint. The package has changed names (back) to angular – dropping the 2. You'll need to update your pubspec.yaml and the corresponding imports in your code. In most instances, find-and-replace should do the trick. Going forward, the package will be called package:angular. We'll just update the version number.
Smaller code The updated compiler in 4.0 allows type-based optimizations that not only improve runtime performance but generate better code because we are able to strongly type templates. A big result of the update is that many ap…

The new AdWords UI uses Dart — we asked why

Google just announced a re-designed AdWords experience. In case you’re not familiar with AdWords: businesses use it to advertise on google.com and partner websites. Advertising makes up majority of Google’s revenue, so when Google decides to completely redo the customer-facing front end to it, it’s a big deal. The Dart team is proud to say that this new front end is built with Dart and Angular 2. Whenever you asked us whether Google is ‘even using Dart for anything,’ this is what we had in mind but couldn’t say aloud. Until now. We asked Joshy Joseph, the primary technical lead on the project, some questions. Joshy is focusing on things like infrastructure, application latency and development velocity, so he’s the right person to ask about Dart.Q: What exactly did we launch on Monday?It’s a complete redesign of the AdWords customer experience that is rolling out slowly as a test to a small initial set of advertisers. The most noticeable thing is probably the Material Design look and f…

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 …