[swift-evolution] Pitch: Cross-module inlining and specialization

Slava Pestov spestov at apple.com
Tue Oct 3 01:20:29 CDT 2017

> On Oct 2, 2017, at 11:11 PM, Slava Pestov via swift-evolution <swift-evolution at swift.org> wrote:
>> This semantic doesn’t make sense to me, and I think we need to change it.  I think we are better served with the semantics of “the body may be inlined, but doesn’t have to.”
> That is the effect it has today. The decision to inline or not is made by the optimizer, and @inlinable doesn’t change anything here; it makes the body available if the optimizer chooses to do so.

Also remember we have the @inline(never) attribute. It’s not underscored so I’m assuming it’s an “official” part of the language. And "@inline(never) @inlinable" is a perfectly valid combination — it serializes the SIL for the function body, and while inlining it is prohibited, it is still subject to specialization, function signature optimizations, etc.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20171002/0749e5ab/attachment.html>

More information about the swift-evolution mailing list