Skip to main content

Notes from Feb 25th Language Meeting: Function Type Annotations, Optional Parameters and Exported Types


The invaluable Bob Nystrom fills us in on the language design discussions taking place amongst Dart engineers. Here are his notes from the February 25 language meeting:


Here's my notes from last week's meeting. I'll have this week's meeting notes out later this week:

function type annotations

Kasper noticed (or maybe someone noticed and brought it to his attention) that there is a place in Dart where seemingly innocuous type annotations do have a runtime effect. Given implicit closurization and is-checks with function types, you can:

1. Store a reference to a method in a variable.
2. Do an is check on that variable against some function type.

For that is check to perform correctly, it means we have to keep track of the methods type annotations at runtime.

The team discussed a bit about whether or not they want to make any changes around this, but didn't come to any conclusions.

optional parameters

We're entering a mode where changing the language gets increasingly hard. We should be careful.

Dan Grove said then if we're going to pull stuff out, we should do it soon. One thing people worry about is parameter syntax with optional parameters and forwarding.

Lars has some ideas for forwarding and will write up a proposal so we have something to discuss.

exported types

I asked if a library B exports Foo from library A and some library C imports both, are those Foos the same type?

I wasn't clear in my question, but after later verifying it myself, it seems Dart does do what I want here:

    // main.dart
    import 'foo.dart' as foo;
    import 'bar.dart' as bar;

    methodTakesFoo(foo.Baz baz) => print("ok");
    methodTakesBar(bar.Baz baz) => print("ok");

    main() {
      var fromFoo = new foo.Baz();
      var fromBar = new bar.Baz();
      
      print('foo.Baz is foo.Baz = ${fromFoo is foo.Baz}');
      print('foo.Baz is bar.Baz = ${fromFoo is bar.Baz}');
      print('bar.Baz is foo.Baz = ${fromBar is foo.Baz}');
      print('bar.Baz is bar.Baz = ${fromBar is bar.Baz}');
      methodTakesFoo(fromFoo);
      methodTakesFoo(fromBar);
      methodTakesBar(fromFoo);
      methodTakesBar(fromBar);
    }
    
    // foo.dart
    library foo;
    
    class Baz {}

    // bar.dart
    library bar;
    export 'foo.dart'; 
 On both the VM (in checked mode) and dart2js, this prints four "true"s and four "ok"s.

And as always, view the changelog for the full list of changes, and to get started with the Editor, see our tutorial.

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 Google AdSense user interface: built with AngularDart

AdSense is a free, simple way to earn money by placing ads on your website. The team just launched a completely new version of their app for publishers. Read all about it here. We asked Daniel White, the tech lead for the project, some questions because the new UI happens to be built with Dart and Angular2.


AdSense launched way back in 2003. How long is it since the last big redesign?
Last big redesign was called ‘AdSense 3’ and launched about 6 years ago. It was written in Google Web Toolkit (GWT) and the UI has evolved through several iterations - but this is the first ground-up redesign in 6 years. There are a number of long-standing UX issues that we’ve taken the opportunity to solve. A big shout-out to our UX team who’ve been 100% behind this project. We couldn’t have done it without them!

How many software engineers worked on the project?
Purely on the AdSense applications, we have a team of close to 100. Around 25% of them write Dart.

How many lines of code?
We have around 160K LO…