> On Jan 25, 2017, at 6:13 PM, Joe Groff <jgr...@apple.com> wrote:
>
>> Naturally, opaque types must limit some optimizations, such as inlining.
>
> I don't see how opaque types by themselves prevent inlining. You can inline a
> generic into another generic, or a function using a resilient type into
> another function.
Good point. I was just hand-waving here about resilient types, which we can’t
inline by design, and archetypes where we can’t inline protocol methods because
method resolution requires specialization. But yeah, we should be inlining
methods on unbound generic nominal types. I updated the doc.
-Andy
_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev
