Motive behind !empty() with front() instead of Optional front()

[Per Nordlöw]

On Thursday, 25 March 2021 at 09:35:40 UTC, deadalnix wrote:
> The big question is, what if I want a range of Optional!T ?

That might lead to confusing code, yes. Aliases or subtypes could 
come of use in such a situation. Better ask the Rust forums...