[Pitch] Extend protocol conformance to consider implicitly defined method signatures

[DevAndArtist (Adrian Meister)]

I also opened a pitch about that issue a while ago, it's a class issue.

Default parameter on init's should satisfy other required init's

There is not much to say here, this is an issue I just encountered now, where I need two different but very similar inits, but for some reason this seems to be not supported yet. Here is a code snippet that forced me to create required convenience override init which in my honest opinion just ugly. Instead it would be far better if default parameter on inits could satisfy other required inits. protocol A { init(foo: String) } protocol B { init(foo: String, closure: (Self) -> Void) } clas…

Writing required convenience override init isn't fun.