>> 1. orElse(null) is still a nuisance. Will this be resolved? > > Thanks for the reminder. This is resolved now, by renaming orElse(Supplier) to orElseGet.