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

AngularDart 4

AngularDart v4 is now available. We've been busy since the release angular2 v3.1.0 in May. Not only did we "drop the 2", but we also improved the compiler and tightened up the framework to give you smaller code, we updated the package structure to improve usability, and we added several new features. Check out the updated documentation to get started.
Just angular Upgrading to v4 will require more than updating your version constraint. The package has changed names (back) to angular – dropping the 2. You'll need to update your pubspec.yaml and the corresponding imports in your code. In most instances, find-and-replace should do the trick. Going forward, the package will be called package:angular. We'll just update the version number.
Smaller code The updated compiler in 4.0 allows type-based optimizations that not only improve runtime performance but generate better code because we are able to strongly type templates. A big result of the update is that many ap…

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…

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 …