Miss Dada  🏳️‍⚧️

I would like to nominate `Option::as_deref` for the worst named method in Rust

what would you call it? ... i remember being kind of frustrated by how long it was unstable because of that particular bikeshed, and it’s really way nicer than .map(|x| &*x)

First preference: `Deref` was just structured in a way it could be implemented by `Option<impl Deref>`. Second preference: Inherent method called `deref` Third+ preference: Something that implies it's *calling* deref on its member, e.g. `derefed`.

how would the first preference work? how do you handle None?

a different signature so you could have Option<A> -> Option<A::Deref>

would this require HKT?