Skip to main content

First Look at new Dart Libraries

The Dart libraries are implementing a common model for processing a stream of events, and you can try the new libraries now with a preview release of Dart Editor. Developers consistently told us they wanted a more unified method for dealing with asynchronous events. The new Streams API from the dart:async library delivers on the vision of a builtin way to listen for, transform, and emit a sequence of events.

Beautiful streams.

There are numerous changes in the new Dart libraries, above and beyond just Streams. Here is a look at what's new, with some tips for migration. Note: this list is not comprehensive. You can explore the API docs to learn more about these new libraries.

Core library

  • Iterable interface is changed. Now uses "bool moveNext()" and "E get current" to advance and read the current value.
  • Iterable interface is greatly extended.
    • Collection methods moved to Iterable, e.g. any and contains.
    • ‘map’ has been renamed to ‘mappedBy’. The result is lazy.
    • ‘filter’ has been renamed to ‘where’. The result is lazy.
    • Many new operations, and some old operations, now work on all Iterables.
    • Iterable transforming methods (those returning a new Iterable) are lazy - that is, they don't create a new collection immediately.
    • Added Iterable.toList() and Iterable.toSet(). This allows easy porting from old code: foo.map(...) -> foo.mappedBy(...).toList()
  • Added optional function argument to int/double.parse which is called in case of a parsing error. Default behavior is to throw FormatException as before.
  • Added optional arguments to int.parse: “radix”. Example: int.parse(“ff”, radix: 16) -> 255.
  • Changed int.~/ to always return an int value.
  • Added String.replaceAllMapped that takes a function to compute the replacement for each match.
  • Removed Sequence class.
  • The generic List constructor is not fixed length anymore if an argument is given. The list’s size can still be changed afterwards.
  • There are two new named List constructors: List.fixedLength(length, {fill}) and List.filled(len, fill).
  • Strings.join now takes an iterable, but Strings will be removed. Iterable now has a join. Also, Arrays will be removed.
  • map.keys and map.values no longer allocate a copy, so avoid modifying the data structure while iterating. Instead, create the copy by using "for (var key in map.keys.toList())"


Collections


  • Added separate collection library, "dart:collection" for implementations and collections beyond plain Map, Set, and List.


Async


  • Library "dart:async" added.
  • Future and Completer moved to async library.
  • Timer moved to async library.
  • Future interface greatly changed. Most importantly:
    • "chain" and “transform” combined into "then" by checking whether the return value of the handler is a Future.
    • Future is now purely asynchronous - you can't read a value or exception directly from the future, but must register an event handler to receive it at a later time.
    • To fix existing uses of Future: Change "chain" to "then". Always register a "then" or "catchError" handler immediately when you receive a future, or you might not catch an error in time.
  • Added Stream: an asynchronous event source. Single or multiple listeners, produces sequences of both value events and errors.
  • As an asynchronous version of Iterable, Stream has async versions of the transforming methods of Iterable.
  • New AsyncError is now wrapping all errors propagated to async event handlers, both on Future and on Stream.



JSON


  • Library interface changed: No JSON class, methods renamed.
  • Added optional "reviver" argument to parse.
  • Removed length method.



HTML


  • For more information, see our mailing list post.
  • on.click.add is now onClick.listen (streamified)

We invite you try your code with the new libraries, join the discussion on the Dart mailing list, and file issues and bugs at the Dart Issue Tracker.

Photo Credit: ecstaticist (cc)

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

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
Read more

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
Read more