Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/323
Do we want to return `empty` for `null`? I ask because the "ergonomics" are
different. The way we have it now:
```
try {
iterator.nextOptional().ifPresent(this::doStuff);
}
catch (NullPointerException e) { worry about that; }
```
vs. just `iterator.nextOptional().ifPresent(this::doStuff);` where
`doStuff` is responsible for testing for `null`. I actually like the latter
because `null` might be a legitimate value, but I may be misunderstanding the
contract of `ExtendedIterator`-- is it guaranteed that `next()` never returns
`null`? Is `null` actually not ever legit?
---
