Skip to main content

Types and casting in Dart

Post by Seth Ladd

Bob Nystrom, engineer on the Dart team, posted a nice response to some questions posed to the mailing list about types, assignments, and casting. I thought this was a good way to phrase the issues, so I am posting here for others to find and enjoy.

Bob's reply to "Using num, one can assign a double to an integer without error or warning?":

"

  num n = 3.56;

Here, we assign a floating point literal whose static type is double to a
variable annotated to be type num. num is a supertype of double so you're
doing an upcast here. Like most languages an upcast is always safe and OK.
No warnings here.

  int x = n;

Here, the static type of n is num and we are assigning it to a variable
whose annotated type is int. int is a *sub*type of num, so in this case we
are doing a downcast. In most statically typed languages, you would need an
explicit cast operator, like:

  int x = (int)n;

Dart is different here. It has something called "assignment compatibility"
to determine which assignments are valid. Most languages just use the
normal subtyping rules for this: an assignment is safe if you assign from a
sub- to a supertype. Dart's assignment compatibility rules also allow
assigning from a super- to a subtype.

In other words, you can *downcast* implicitly in an assignment, without
needing any kind of explicit cast. So there's no *static* warning here.
However, if you run the code in checked mode and that downcast turns out to
be invalid (as it is here), you *will* get a type error at runtime when you
try to assign a double to x.

By analogy to Java, your code is similar to:

Object n = 3.56;
Integer x = (Integer)n;

A Java compiler will allow this, but it will fail at runtime. The main
difference from Dart is that in Java you need that explicit (Integer) cast
to downcast.
"


Thanks to Ross, Ladislav, and Bob, for chiming in and helping with the original question. You can chime in, too, in the Dart mailing list.

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

A stronger Dart for everyone

We are constantly asking ourselves:
How do we make developers even more productive when writing Dart apps? We believe that a critical part of the answer to this question is to make strongmode – a sound static type system for Dart – the standard for all Dart developers.

Teams that use Dart to build apps like Soundtrap, AdWords, AdSense, and Greentea say they really enjoy using strong mode features, such as early error detection. In fact, teams that have switched completely to strong mode cite not only early error detection but also better code readability and maintainability as major benefits. We hear this both from small teams and Рeven more so Рfrom large teams with hundreds of developers writing and maintaining millions of lines of Dart code. As Björn Sperber from Soundtrap says,
Strong mode and the smooth integration with IntelliJ is a joy to use and a huge improvement. If you’ve tried out Flutter, you’ve already used strong mode checks from the Dart analyzer.

Given the benefits …

AngularDart 2.1 and new Components

AngularDart got its own dedicated team 5 months ago. Last month, we launched 2.0 final on the Dart Developer Summit. Today, we’re releasing the first minor release after that: 2.1.

Since the focus of AngularDart is Productivity, Performance, Stability, there are no major breaking changes (see the changelog) — but a lot of behind-the-scenes improvements. Your apps will get slightly smaller and faster (even relative to 2.0 which already made huge strides in size and performance since the compiled-from-TypeScript days).

Many features that AngularJS had to implement for JavaScript and TypeScript are not needed in Dart (because Dart already has those features out-of-the-box). So we’re removing them from AngularDart. Renderer is deprecated in favor of plain-old dart:html. NgPlural is going away — Dart programs can use the package:intl library.

New components

On the Dart Developer Summit, we launched AngularDart Components — the material design widgets Google is using in customer-facing apps …