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

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 improve applicat…

The new Google AdSense user interface: built with AngularDart

AdSense is a free, simple way to earn money by placing ads on your website. The team just launched a completely new version of their app for publishers. Read all about it here. We asked Daniel White, the tech lead for the project, some questions because the new UI happens to be built with Dart and Angular2.


AdSense launched way back in 2003. How long is it since the last big redesign?
Last big redesign was called ‘AdSense 3’ and launched about 6 years ago. It was written in Google Web Toolkit (GWT) and the UI has evolved through several iterations - but this is the first ground-up redesign in 6 years. There are a number of long-standing UX issues that we’ve taken the opportunity to solve. A big shout-out to our UX team who’ve been 100% behind this project. We couldn’t have done it without them!

How many software engineers worked on the project?
Purely on the AdSense applications, we have a team of close to 100. Around 25% of them write Dart.

How many lines of code?
We have around 160K LO…