Skip to main content

Notes from 5/28 Dart Language design meeting

Posted by Bob Nystrom

Sorry for the long delay. This meeting was just skimming over a bunch of issues in the bug tracker, so forgive me if there isn't a lot of context here.

Import syntax

Kasper and Ivan did the original syntax design. If we want to iterate on that, we should get them in a room.

Catch syntax

Looks weird because it's more like a variable declaration than a parameter declaration. Gilad says we'll figure it out soon and should be a minor change.

Statics in interfaces

Kasper: People find default classes hard to follow. We could consider allowing simple redirect code for constructors in interfaces.

Instance field should be allowed in initializer expression when it is initialized via "this.foo" sugar.

Bug 3263. Gilad says: if the sugar doesn't do what you want, don't use the sugar.

Private names

Dart uses isolates for security, so we don't feel pressure to have JS-private-names-style security.

The default implementation of an interface must not over-specify generic paramaters

Bug 3279. We're OK with the current semantics.

Abstract or static method named the same as enclosing class

Bug 3284

Kasper: The VM is slightly broken with respect to reporting. We should clarify the spec.
Lars: It is very confusing.
Gilad: That's why shadowing is a warning.
Kasper: Should say that if it's the same name, it must be a constructor. If it has a return type or abstract, that's an error.

Function expression vs statements

Can we get rid of return types and/or names?

Bob: Idiomatic dart doesn't have return types or names for function expressions. The style guide may discourage it soon. [ed: it does now.]
Kasper: Getting rid of return type for function expression gets rid of the nasty infinite lookahead with generic return types.
Gilad: What about contexts where you can't distinguish between expr or stmt?
Kasper: If it has a return type or a name, it's a statement. Done. It must be in statement position.
Gilad: Let me try to come up with some rules for it to see if it hangs together.

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