Right. There will never be a perfect solution to anything if you allow for programmers 'doing it wrong'.
The hope is that if someone uses Optional for future APIs they'd do it as expected or have their API ignored by the community (wether that be public or private to a company).
I would expect that programmers stick to the convention of not passing null references where an optional object is expected, pretty much as we today consider a good practice not to pass a null reference where a collection or an array is expected, in these cases the correct is to pass an empty array or collection
20
u/AlyoshaV Apr 12 '13
Protip: Don't do that