> On Aug 1, 2017, at 8:02 AM, Taylor Swift via swift-evolution > <[email protected]> wrote: > > I think the Server APIs project was pretty close to what I had in mind > actually. I don’t see why more core libraries can’t be commissioned that way, > things like Math and DateTime would probably draw a great deal more attention > than Server APIs since they are used by more people. One thing that would > have to be fixed though is the cross-module optimization problem; no one in > their right mind should ever be making generic calls to sin(x). A feature in > the SPM that would perform “injection” of core library code into the interior > of modules would probably be enough to fix this problem for now. (If this > sounds hacky just remember that right now everyone seems to be copying and > pasting .swift files everywhere.) Everything internal would become > fileprivate and everything public would become internal. A good Swift library > should expose no more than 7 or 8 symbols at the top level so this should > play nice with most client projects. >
This is already planned as part of how Modules will be able to control what is and is not part of their ABI: https://github.com/apple/swift/blob/master/docs/LibraryEvolution.rst#inlineable-functions > On Tue, Aug 1, 2017 at 4:50 AM, Ian Partridge <[email protected] > <mailto:[email protected]>> wrote: > On 1 August 2017 at 04:46, Taylor Swift via swift-evolution > <[email protected] <mailto:[email protected]>> wrote: > > I’m not saying the Swift team should devote any time or resources to writing > > these things, but it’d be a huge benefit if someone were to say “okay we are > > commissioning a core library that does X, the code will live in Y Github > > repository, we’ve set up Z mailing list for this, and anyone who is willing > > to invest time in this is welcome to help make this a reality”. Then > > everyone with an interest in seeing these things get built would be able to > > coordinate. > > That's what's happened with the Server APIs Project > https://swift.org/server-apis/ <https://swift.org/server-apis/> > > I would like to see more of this, and math/BigNum seems like a good candidate. > > Another is a modern date/time package, standing on the shoulders of > https://jcp.org/en/jsr/detail?id=310 <https://jcp.org/en/jsr/detail?id=310> > and similar. > > -- > Ian Partridge > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
