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

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 3.0: Easy upgrade, better performance

AngularDart 3.0 is now available. It brings better performance and smaller generated code, while also making you more productive.


Version 3.0 is an evolution: although it has some breaking changes (detailed below), it is a smooth upgrade due to minimal public API adjustments. Most of the progress is under the hood—in code quality, stability, generated code size, performance, and developer experience.

Code quality:
2731 instances of making the framework code more type safe (using sound Dart).The AngularDart framework code size is down by 12%.Many additional style updates to the codebase:Changed to use idiomatic <T> for generic methods.Removed NgZoneImpl, all the code exists in NgZone now.Stability:
Many CSS encapsulation fixes due to update with csslib package.Fixed bugs with IE11.

Performance:
For the Mail sample app, we see 30% faster time-to-interactive (currently 3812 ms on a simulated 3G connection, measured via Lighthouse).Our large app benchmark shows 2x faster render times of…

Dart 1.24: Faster edit-refresh cycle on the web & new function type syntax

Dart 1.24 is now available. It includes the Dart Development Compiler and supports a new generic function type syntax. Get it now!


Figure 1: DDC debugging in Chrome.

Some notable changes in this release:
pub serve now has support for the Dart Development Compiler. Unlike dart2js, this new compiler is modular, which allows pub to do incremental re-builds for pub serve.In practice what that means is you can edit your Dart files, refresh in Chrome (or other supported browsers), and see your edits almost immediately. This is because pub is only recompiling your package, not all packages that you depend on.There is one caveat with the new compiler, which is that your package and your dependencies must all be strong mode clean.You can also use the new compiler to run your tests in Chrome much more quickly than you can with dart2js.Read more in the changelog.You can now publish packages that depend on the Flutter SDK to pub. Moreover, pub.dartlang.org has started tagging Flutter plugins with …