Pitch: allow optional assignment in failable init

[taylorswift]

@Jumhyn

Am I understanding the idea correctly that self = nil would immediately exit the init? If so my main concern is that this syntax would obscure control flow in more complex cases—a seemingly benign assignment, even if you're fully aware of the types involved, would behave quite differently from a similar assignment outside of an init?.

what if instead of using assignment, we were to go the opposite direction and say that we can return an instance of Self? from a failable init, and that would be the same as conditionally assigning to self?

extension SpecializedType:LosslessStringConvertible
{
    public
    init?(_ description:__shared String)
    {
        return GenericImpl<T>.init(description).map(Self.init(value:))
    }
}