Skip to main content

Dart Team Updates and Notes

Posted by Seth Ladd


Summary

  • Summer vacations are wrapping up, back to work! The Dart project ramps up for the M1 release, which delivers a more stable language and implementations.

Details

Dart language specification:

  • Version 0.11 is almost ready - this is pretty much the M1 version.
  • Mixin proposal to be published.

Dart libraries [core, unittest, i18n, etc]:
  • Ability to make temporal assertions with the mocking library
  • Work in progress on sharing the source for the dart: library implementations across VM and dart2js.

Dart VM:
  • New language features implemented: “non-constant initializers for fields” (bug 3848), “static methods are compile-time constants” (bug 3406), “operator syntax” (bug 3767), “getter syntax” (bug 3608), “on-catch support” (bug 3757).
  • Switched to using SSA-based optimizing compiler both on ia32 and x64.
  • Using type propagation to eliminate assignability checks to improve checked mode speed.
  • Added support for external and patch to enable shared core library sources.
  • 20% decrease in initial heap size for new isolates.

Dart to JavaScript Compiler:
  • Improved noSuchMethod handling to limit the explosion in code size that used to arise from using the feature anywhere in the code base.
  • Started propagating type information through parameters to generate smaller and faster output.
  • Introduced basic framework for providing type information to the compiler backend, which will be used to experiment with global concrete type inferencing.

  • Added primitive support for external and patch to enable shared core library sources.

dart2dart:
  • Close to be able to bundle the whole dart2js into a monolithic Dart file

Dart Editor:
  • An initial implementation of a 'Create Method' quick fix. This will create a method definition to satisfy a reference to a non-existent method. You can access this functionality through the ctrl/command-1 keystroke; currently only top-level functions are supported.
  • Several analysis fixes and various updates to our analysis code for M1 language support.
  • We now include optional parameters in completion proposals.
  • There is a new Breakpoints view to view your debugger breakpoints.
  • Enhanced ‘Open Folder...’ to better support opening very large applications.
  • Fixes to the Apps view and enhancements to our Welcome page.

Dart UI [dart:html, web components]:

Dart SDK and build:
  • /lib being split into /lib and /pkg well underway.

Pub:
  • Read-only site for pub.dartlang.org (not live yet).
  • Support for installing packages from a package hosting site (like pub.dartlang.org when it’s up).
  • Windows support for Pub is coming along.
  • New documentation with more coming.

Dart Server [dart:io, etc.]:
  • Work in progress on HTTPS support.

Dart Dev Rel:
  • Auto-publish API docs on successful build.
  • Added a page on Dart books
  • More episodes of Dartisans

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