[swift-evolution] Pitch: (Almost) std libs

Jordan Rose jordan_rose at apple.com
Wed Jan 27 10:52:35 CST 2016

> On Jan 26, 2016, at 23:32 , David Turnbull via swift-evolution <swift-evolution at swift.org> wrote:
> On Tue, Jan 26, 2016 at 10:44 PM, FĂ©lix Cloutier <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
> This is probably what David means when he says that it uses dynamic dispatch.
> I was a bit imprecise because 100% of my math libraries are generic. So it's stuck in my head that everything gets a dynamic dispatch. But yeah, concrete functions crossing modules are simply not-inlined. Which is still a very big deal for simple math operations.
> Regardless of the technical details, there's significant advantages to being "stdlib" instead of "module". That's what I wanted to bring to the discussion. It's not something you'll find in the docs but I think it's important to know about for anyone working on this idea.

It isn't a "stdlib" vs. "module" distinction. The core standard library is compiled in an incredibly hacky mode that has pretty much broken something every time we try to extend it to something else; there are a number of bugs across the compiler that we need to fix so that we can do this reliably for arbitrary modules (without any customization). Some of the issues are listed at the bottom of the TransparentAttr.rst <https://github.com/apple/swift/blob/master/docs/TransparentAttr.rst> document, for lack of a better place to put them.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160127/4ec9bf1e/attachment.html>

More information about the swift-evolution mailing list