Re: exposing only what you want - headers and Swift?

Jim, When you ship a Swift framework it does not contain source code. But if you want to give someone else the ability to build the framework (say because you don’t support a specific compiler version or specific ABI, or so unneeded parts can be left out), you must ship the source. Some

Re: exposing only what you want - headers and Swift?

Don’t you have to ship your Swift source code with a framework because of source incompatibility and ABI issues? On Jun 26, 2016, at 3:06 PM, Thomas Wetmore > wrote: A framework does not include source. It as an opaque bundle that contains a public

Re: exposing only what you want - headers and Swift?

A framework does not include source. It as an opaque bundle that contains a public API and compiled code as an integrated whole. > On Jun 26, 2016, at 2:48 PM, William Squires wrote: > > True, but they'd still have the source .swift file as the compiler would need > this

Re: exposing only what you want - headers and Swift?

On Jun 26, 2016, at 11:48 , William Squires wrote: > > they'd still have the source .swift file as the compiler would need this to > know what symbols, identifiers, etc... there were, even if they were marked > private No, only the public symbols would be in the

Re: exposing only what you want - headers and Swift?

True, but they'd still have the source .swift file as the compiler would need this to know what symbols, identifiers, etc... there were, even if they were marked private. Whereas in ObjC, I can give someone the header and the framework, and they can't see the internals, and thus be tempted to