> On Jun 29, 2016, at 4:38 PM, Brent Royal-Gordon via swift-evolution
> <[email protected]> wrote:
>
> Additionally, I believe the other un-defaulted associated types we'd like to
> infer if we can—`Collection.Index`, `Sequence.Iterator`, and
> `IteratorProtocol.Element`—could all be handled by simple "caveman inference"
> heuristics, rather than a full type inference pass. All three of these are
> used in either the types of un-defaulted properties (which cannot ever be
> overloaded) or the return types of un-defaulted nullary methods (which can be
> overloaded but rarely are). If we could use only those limited cases to guess
> the appropriate types, then plug them in and see if they typecheck, that
> would go a long way towards softening the blow of removing associated type
> inference.
I’m curious about this too. It seems too easy...
Russ
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
