Explore using SPM modules to allow specific imports of components.

[mhdostal]

No description provided.

[dfeinzimer]

Not sure this carries over to Swift packages but I found the following in this article:

As far as performance and binary size goes, any unused symbols are already optimized out of the final binary by the Swift compiler. If there’s no reference to it at compile time then it’s removed, meaning that importing a framework but not using particular parts of it shouldn’t have any negative implications.

[mhdostal]

@dfeinzimer Thanks for that. Swift-Numerics has modules that you can import. You still have to include the whole Package in your project, but in individual files you can just import the bits you need. This is accomplished by having separate "Targets" in the "Package.swift" file. I'm not sure if this helps any (maybe with app size?); there doesn't seem to be a whole lot of documentation on it.

[rolson]

Since the toolkit will be added as a source dependency to an app, the compiler should strip out anything that is not needed. So if you were only using the authenticator, then you wouldn't bloat the binary with other components you aren't using.

[philium]

I don't know if included frameworks would be stripped. It would be good to verify that.