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

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

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