Skip to main content

Notes from January 7 language meeting

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

Here's my notes from this week's meeting:

call() versus operator()

Gilad brought up the perennial discussion of how classes that emulate functions should define that operation: as a method named call() or using an operator syntax.

Lars: What are problems with making it an operator?
Gilad: At this point I think we could. It's an incompatible change, but not a big deal.

Configuration-specific code

Gilad has a rough proposal he's working on for this.

Method cascade grammar

[Bob: I think the Dart implementations and spec are out of sync regarding how they handle precedence of method cascades in particular with respect to the ternary operator.]

Gilad: The grammar for cascades makes sense from perspective of someone looking at the grammar, but not as much for someone trying to program using them.

Kasper: There are a couple of corners of the grammar that are confusing and there have been bugs filed. Maybe we should take a look at moving some things around.

Lazy loading libraries

Lars: Something to move up on the list is lazy loading. Aarhus has started working on this.

Kasper: Should be able to compile into multiple specific files that are loaded somehow on demand and can be stitched together.

Gilad: This and configuration-specific code are somehow related.

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

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…