[swift-evolution] private & fileprivate
clattner at apple.com
Mon Oct 10 19:55:21 CDT 2016
On Oct 8, 2016, at 12:15 PM, Matthew Johnson via swift-evolution <swift-evolution at swift.org> wrote:
> There are rather significant optimization barriers at module boundaries right now. These do not exist for the standard library due to its tight relationship with the compiler, but for the moment it is a non-trivial concern for 3rd party code that is performance sensitive. This is effectively a language pressure in the direction of larger modules, at least for some domains. (Hopefully this pressure will eventually be alleviated - there has been at least some talk in that direction)
Indeed, I expect that this will be a big focus over the next year. The resilience model and ABI stability drive the urgency of getting this worked out.
More information about the swift-evolution