Skip to main content

Notes from the March 18 Dart Language Design Meeting


Once again, the always-helpful Bob Nystrom fills us in on the language design discussions taking place amongst Dart engineers. Here are his notes from the March 18 language meeting:

proxies

Lars: I like the "implements dynamic" thing.
Gilad: Me too, it's like a get out of jail free card.
Kasper: That means the type behaves like dynamic in all contexts? Even for is checks and checked mode checks?
Gilad: If you assign something to it, it goes through normal rules. But if you assign it to something, works like dynamic. It could go both ways.
Lars: The real solution would be to do it dynamically. Like you have noSuchMethod, you could have isSubtype on ClassMirror that returns a boolean. You could implement that to do what you want.
Gilad: That's complicated to implement.
Lars: Let's talk about the first solution with Ivan and Kasper.
Kasper: That means it will be a subtype of all types. If a class claims it implements dynamic and List, should you get warnings if you implement list methods incorrectly? Are we going to say it's illegal to implement list too?
Gilad: It's legal, but stupid. It won't change anything at all.
Lars: My perspective is, given that this is a corner case, I'm fine with it not having any effect if you also say you implement List.
Gilad: We could say implementing dynamic just affects subtyping, but you still get the same warnings internally in class.
Lars: I'm fine with that too.
Gilad: OK, i'll send around a proposal.

optional arguments and forwarding

Lars: No one is screaming for [the forwarding operator], so we'll just ignore it.
Gilad: Do we use "?" on its own?
Lars: It's being used a lot, so we keep it. As long as you aren't forwarding it's fine. Maybe we need to look at the reflective interface for calling methods. If we implement this proposed solution, it probably won't be used other than in a few places.
Kasper: Where are the uses of "?"? In the DOM mostly?
Lars: There's a lot in the DOM but in other places to.
Kasper: It's not a question of forwarding, but of being forwarded to.
Lars: I'm fine either way. I find it harder to read using null. It's hard to remove things because people are already screaming about breaking lib changes.

lazy loading

Lars: Gilad, are you up on what's going on there?
Gilad: I've seen the patches, but it's not in spec. I haven't had time to talk to Peter yet, but I'm tracking it.
Kasper: We haven't figured out if we want same solution on VM.
Gilad: I assumed that. What does that mean?
Lars: As a minimum, we need the same code to run there.
Kasper: Yes, load() should do something minimal.
Gilad: It would be nice if it actually could defer it.
Lars: I'm fine with the VM preloading it.
Gilad: In that case, it doesn't belong in spec because it has no particular behavior. It's a dart2js deployment detail.
Lars: Yes, easiest solution is to keep out of spec.

Cheers!

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

Const, Static, Final, Oh my!

Posted by Seth Ladd

(This is an "oldie but a goodie" misc@dartlang.org post originally written by Bob Nystrom. It is being posted here as the explanations still ring true.)

Bob writes:


"static", "final", and "const" mean entirely distinct things in Dart:

"static" means a member is available on the class itself instead of on instances of the class. That's all it means, and it isn't used for anything else. static modifies *members*.

"final" means single-assignment: a final variable or field *must* have an initializer. Once assigned a value, a final variable's value cannot be changed. final modifies *variables*.

"const" has a meaning that's a bit more complex and subtle in Dart. const modifies *values*. You can use it when creating collections, like const [1, 2, 3], and when constructing objects (instead of new) like const Point(2, 3). Here, const means that the object's entire deep state can be determ…

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…