Skip to main content

Dart Language progress update

Posted by Gilad Bracha


The Dart language team gathered to discuss some of the open issues with the language.


Language Bugs: Will review language bugs and either fix, mark as deferred to future release (meaning no decision but distinctly possible in the future) or close. 30 bugs already processed last week.

Cascades: The new dart2js compiler has implemented the spec. We will review to see if spec needs minor adjustments in light of implementation experience. We don’t expect any significant changes.

Defaults in interfaces:  We expect to support these. Intended semantics are to give a warning if violated by implementor. However, if no default is given in the interface we will not interpret that as a default of null.  People can override in the default code if they want to, and may have reason to.  In any case we have no way force them to do otherwise. We will pin down draft specification.

Generics reification: We discussed whether to back off of that. The decision is to retain reification unless major problems arise in dart2js. We do not anticipate such problems, but once dart2js implements the semantics we can quantify any costs.

Multiple initialization points for finals:  Tendency is to keep current spec and fix implementation, but we do need to see what impact it has on code base. Ongoing discussion.

Repeated keys in map literals: We noted that we could disallow this if the keys are strings constants, but since we are hoping to generalize that, it might not make any sense.

Switch statement: Decision is to restrict switch to operate on compile time constants of uniform type - either int or String. We could extend this to enums if we ever add them. The motivation is that switch is only useful as a highly optimized jump table, and so we should focus on that; otherwise use if-else, it’s clearer. We will adjust spec accordingly.

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