On 04/14/2014 09:29 AM, Viktor Klang (√) wrote:

> This means that a Promise can never have |null| as a valid value.

Deja vu. Coping with this (and the many conventions people
adopt surrounding it) is the ultimate reason that
CompletableFuture has so many methods dealing with so many
different functional forms. To keep reactive-streams
simpler, you may want to banish null arguments and results
by requiring that methods throw exceptions?

-Doug