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

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