Re: [swift-evolution] Swift 4: Support for static libs / modular development.

2017-02-17 Thread Raphael Sebbe via swift-evolution
Sure, thank you. If SwiftPM gets a working integration in Xcode 9, that could do it. Raphael On Fri, Feb 17, 2017 at 1:50 PM Ole Begemann <o...@oleb.net> wrote: > > > On 17 Feb 2017, at 10:28, Raphael Sebbe via swift-evolution < > swift-evolution@swift.org> wrote: >

[swift-evolution] Swift 4: Support for static libs / modular development.

2017-02-17 Thread Raphael Sebbe via swift-evolution
I'm not fully aware of the state of discussion, so sorry if it is already being addressed. I wanted to bring some feedback and awareness about the need of a supported way to build app components as *static libraries* in Swift. We've moved most of our new developments to Swift 3. Our apps are

Re: [swift-evolution] [swift 4] static libs/modular code, fixed-size arrays, ref/pointer to structs, pointers, numeric types.

2016-08-05 Thread Raphael Sebbe via swift-evolution
thank you Ankit for that information. Do you mean a single (SwiftPM) repository could handle the 5 static libs I was mentioning in my first mail, with apps linking selectively with those, as opposed to entire module/product? That'd be great. Also, what about the state of integration in Xcode,

Re: [swift-evolution] [swift 4] static libs/modular code, fixed-size arrays, ref/pointer to structs, pointers, numeric types.

2016-08-04 Thread Raphael Sebbe via swift-evolution
Thank you Chris, James. I'm answering James feedback/questions below. On Thu, Aug 4, 2016 at 1:57 AM James Froggatt wrote: What are your thoughts on using tuples for this? > > typealias CGPoint4 = (CGPoint, CGPoint, CGPoint, CGPoint) > > struct Quad { var corners:

[swift-evolution] [swift 4] static libs/modular code, fixed-size arrays, ref/pointer to structs, pointers, numeric types.

2016-08-03 Thread Raphael Sebbe via swift-evolution
Heard about the Swift 4 thing, so here are a few thoughts about the current version of Swift (3). We work on a sizeable code base, with a focus on modular code that is shared across our apps. Sorry if these things have been discussed already, just joined, and wanted to share a snapshot of our