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.

Mixins

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.

Cheers!

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).

AngularDart is going all Dart

Until now, the multiple language flavors of Angular 2 were written as TypeScript source, and then automatically compiled to both JavaScript and Dart. We're happy to announce that we’re splitting the Angular 2 codebase into two flavors – a Dart version and a TypeScript/JavaScript version – and creating a dedicated AngularDart team.

This is amazing news for Dart developers because:

The framework will feel more like idiomatic Dart.It will make use of Dart features that couldn't work with the TypeScript flavor. It will be faster.
This is equally great news for our TypeScript and JavaScript developers, by the way. Cleaner API, performance gains, easier contributions. Read more on the Angular blog.

Angular 2 for Dart is used by many teams at Google. Most famously by the AdWords team, but many other Google teams build large, mobile-friendly web apps. Some of the top requests from these teams were: make the API feel like Dart, provide a faster edit-refresh cycle, and improve applicat…

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…