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

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 3.0: Easy upgrade, better performance

AngularDart 3.0 is now available. It brings better performance and smaller generated code, while also making you more productive.


Version 3.0 is an evolution: although it has some breaking changes (detailed below), it is a smooth upgrade due to minimal public API adjustments. Most of the progress is under the hood—in code quality, stability, generated code size, performance, and developer experience.

Code quality:
2731 instances of making the framework code more type safe (using sound Dart).The AngularDart framework code size is down by 12%.Many additional style updates to the codebase:Changed to use idiomatic <T> for generic methods.Removed NgZoneImpl, all the code exists in NgZone now.Stability:
Many CSS encapsulation fixes due to update with csslib package.Fixed bugs with IE11.

Performance:
For the Mail sample app, we see 30% faster time-to-interactive (currently 3812 ms on a simulated 3G connection, measured via Lighthouse).Our large app benchmark shows 2x faster render times of…