Type resolution/equality rules in protocol extensions (or: why does Swift give my associatedtype a default value?)

[Lantua]

@lukas

Question #1: Why does this compile? Why does Swift use Never as the default type for S.Value ?

There is this post: What kind of magic behavior is this?. I believe it was intentional to infer the associated type this way, though some did say the type inference is unnecessarily aggressive.

Now sure how much has changed since then, though.