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)

Comments

Popular posts from this blog

Const, Static, Final, Oh my!

Posted by Seth Ladd

(This is an "oldie but a goodie" misc@dartlang.org post originally written by Bob Nystrom. It is being posted here as the explanations still ring true.)

Bob writes:


"static", "final", and "const" mean entirely distinct things in Dart:

"static" means a member is available on the class itself instead of on instances of the class. That's all it means, and it isn't used for anything else. static modifies *members*.

"final" means single-assignment: a final variable or field *must* have an initializer. Once assigned a value, a final variable's value cannot be changed. final modifies *variables*.

"const" has a meaning that's a bit more complex and subtle in Dart. const modifies *values*. You can use it when creating collections, like const [1, 2, 3], and when constructing objects (instead of new) like const Point(2, 3). Here, const means that the object's entire deep state can be determ…

Dart 1.12 Released, with Null-Aware Operators and more

Dart 1.12.0 is now released! It contains the new null-aware operators language feature, and enhancements to pub, Observatory, dartdoc, and much more.

Null-aware operators

The new null-aware operators help you reduce the amount of code required to work with references that are potentially null. This feature is a collection of syntactic sugar for traversing (potentially null) object calls, conditionally setting a variable, and evaluating two (potentially null) expressions.

Click or tap the red Run button below to see them in action.

??

  if null operator. `expr1 ?? expr2` evaluates to `expr1` if not `null`, otherwise `expr2`.


??=

  null-aware assignment. `v ??= expr` causes `v` to be assigned `expr` only if `v` is `null`.

x?.p

  null-aware access. `x?.p` evaluates to `x.p` if `x` is not `null`, otherwise evaluates to `null`.

x?.m()

  null-aware method invocation. `x?.m()` invokes `m` only if `x` is not `null`.

Learn more about Dart's null-aware operators in our Language Tour.

.packages fi…

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 Design look and f…