Skip to main content

Breaking Change! NullPointerException Removed


If you have the NullPointerException in your code, its time get rid of it.

Lasse Nielsen writes:
The ugly duckling of exceptions, the NullPointerException, has been removed.

It had numerous problems. The two most immediate ones were that there wasn't a pointer, and it wasn't an exception. And it was causing confusion, most visibly by its being used inconsistently:

  • It should, by the spec, be a subclass of NoSuchMethodError (and hence be an error), and be thrown by Null.noSuchMethod.
  • It should also be thrown if you tried to throw the null object - which matched badly with being a NoSuchMethodError.
  • And it was being thrown by methods that couldn't handle a null argument value. This was Java style, because it allowed you to skip a test in Java and just use the object and still get the same exception. 

Without NullPointerException, those three cases now need to be handled independently:
  • Accessing a missing member on null will throw a NoSuchMethodError, just like on any other object. The receiver will be null, so we can format the error message specially if we want it.
  • Throwing the null object now throws the new NullThrownError. 
  • Invalid arguments should be reported by an ArgumentError, even if the invalid argument is null.

In Dart, null is not (that) special. It's just an object like any other. The things that make it special are basically:
  • Type assertions always accept it - that's what "nullable types" means in Dart.
  • It's returned automatically by functions without a return (or with a "return;" statement).
  • You can't extend Null - and wouldn't be allowed to, even if the type was visible.
  • You can't throw it (which is just a choice, not something inherently required by the Dart object model).

Change landed in r15136.
 
As always, we invite you to join our Dart mailing list, ask questions on Stack Overflow, or file feature requests on dartbug.com.

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 …