Skip to main content

Dart Language meeting notes from Sept 17

Bob Nystrom posted the latest Dart language meeting notes to the mailing list. Bob writes:


Here's my notes from this weeks meeting:

0.11 language spec

I asked when we'd be publishing the next version of the language spec. Gilad says "real soon now". We keep making changes so we don't want to publish just to immediately invalidate something a few days later.

scope of type parameters

Gilad brought up what happens if you try to access a type parameter within a static method:

class Foo<T> {
  static bar() => T; // <- What does this mean?
}

Currently they are just not in scope, which means it could refer to some other outer name.

Instead, maybe we should say they are in scope, but you can't use them, which is consistent with other names inside a class.

Kasper says there one's scope. It doesn't matter whether you are on the instance or static side. You'll just get an error if you try to refer to something from the wrong side.

warnings on built-in identifiers

Gilad wonders if the warnings aren't helpful for things like "get" and "set" even though they are allowed. We discussed not showing a full warning but maybe some sort of "suggestion" that you shouldn't do that. We've decided to drop the warnings.

limited stack traces

The language spec was changed recently to state that when you get a stack trace in a catch, it only includes the stack frames from between the throw and the catch, but nothing past that. This means users can't get the full context for how an exception was reached.

Lars said the intent was can look at the catch handlers on the stack to see if you need to collect stack trace at all. We never intended it to be partial stack trace. The semantics were always intended to be entire stack trace.

Gilad will update the spec.

cascaded calls in initializer expressions

Right now, you have to parenthesize them, and we're not sure why. Gilad will look into the grammar and see if it doesn't work out.

lowercase string

Kasper said early on they discussed aliases for things like Integer -> int. But then they figured people would use a mishmash of both, which would be ugly and inconsistent. Instead, they chose to go with a single name for each built in type.

Lars said they looked at the built-in types and picked a list of them that they felt should have easier lowercase names. They didn't want all of them, so they had to draw the line somewhere. They are happy with "String" as it is.

Cheers!

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…