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

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…