Skip to main content

Notes from November 5th Language Design Meeting

Dart engineer Bob Nystrom has posted the notes from the November 5th language design meeting. He writes:

Here's my notes from last week's meeting. There's no meeting this week, so this will have to tide you over. :)

NoSuchMethod and ()

Lars brought up bug 6428.

In Dart, if you call foo(), you get a noSuchMethod error for method "foo". If you call (foo)(), you get noSuchMethod error for getter "foo". This is how the language is specified and it's the behavior the designers expected, but dart2js doesn't currently do it correctly, and the behavior may be unintuitive.

Gilad says he'll look at the bug.

Forwarding

Lars: If you want to forward something with optional params. Right now you cannot.
Gilad: I want to look at it some more. I'd like to reuse mechanism.
Bob: We realized this in Seattle shortly after the new signature stuff came out. After some discussion, our guideline is just "never use that question mark operator thing" since it breaks forwards.
Lars: The problem is not the question mark operator. Cannot cleanly do pass-along in noSuchMethod either.
Gilad: Question operator was part of solution but doesn't work in all cases.

There's more context on this here: http://code.google.com/p/dart/issues/detail?id=6496.

Configuration-specific code

Lars: We handle this in the core libraries using patch but we don't definitely don't want to expose that to the world. We need a solution. Proposals are welcome, but would really like something that's extremely simple.

"abstract" modifier

Gilad: It's gone, right?
Bob: Is it optional or gone?
Lars: We originally planned to make it optional but we discussed it some more. If you make it optional, you get stylistic wobble. Some people will use it and some won't. If it's optional, we couldn't find good places where it made sense to put it in.
Lars: So decision as of today is that abstract is not allowed for members.

Call operator and call() method on SendPort

In the spec, when you do foo(), if foo is an object with a call() method, it desugars to invoking that. Unrelated, SendPort has a method named call().

Gilad: Don't want to be able to call on a SendPort using just parentheses. Should we renamed the method, or consider changing the language to have an actual operator ()?  There's a lot of moving parts so not sure if we want to do this.
Lars: The operator would be more symmetric with how its called. Is this is a pressing issue?
Gilad: Presumably it will get implemented soon and people may start using the current semantics.
Lars: Can you file a bug to track it?

Wrong number of type arguments

Gilad: We intended to change it from an error to a warning.
Lars: What are the semantics?
Gilad: If it has the wrong number of type arguments, it will throw at the constructor.

Shadowing setters

Lars: Have an open issue about pairwise shadowing of fields.

Here's an example. Start with this:

    class Foo {
      var bar;

      method() {
        var bar = 1;
        bar = 2; // assign to local
      }
    }

Now change it to:

    class Foo {
      var bar;

      method() {
        final bar = 1; // var -> final
        bar = 2; // call setter!
      }
    }

We should look at some sort of pairwise shadowing. Otherwise it's too surprising.

We all agree this should be solved. We can work on this when we are in person.

Cheers!

As always, we invite you to join our Dart mailing list, ask questions on Stack Overflow, or file feature requests on dartbug.com.

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…