Swift Numerics provides a set of modules that support numerical computing in Swift. These modules fall broadly into two categories:
There is some overlap between these two categories, and an API that begins in the first category may migrate into the second as it matures and new uses are discovered.
Swift Numerics modules are fine-grained. For example, if you need support for Complex numbers, you can import ComplexModule¹ as a standalone module:
import ComplexModule let z = Complex<Double>.i
There is also a top-level
Numerics module that re-exports the complete public interface of Swift Numerics:
import Numerics // The entire Swift Numerics API is now available
Swift Numerics modules have minimal dependencies on other projects.
The current modules assume only the availability of the Swift and C standard libraries and the runtime support provided by compiler-rt.
Future expansion may assume the availability of other standard interfaces, such as BLAS (Basic Linear Algebra Subprograms) and LAPACK (Linear Algebra Package), but modules with more specialized dependencies (or dependencies that are not available on all platforms supported by Swift) belong in a separate package.
Because we intend to make it possible to adopt Swift Numerics modules in the standard library at some future point, Swift Numerics uses the same license and contribution guidelines as the Swift project.
To use Swift Numerics in a SwiftPM project:
.package(url: "https://github.com/apple/swift-numerics", from: "0.1.0"),
Numericsas a dependency for your target:
.target(name: "MyTarget", dependencies: [ .product(name: "Numerics", package: "swift-numerics"), "AnotherModule" ]),
import Numericsin your source code.
Swift Numerics is a standalone library that is separate from the core Swift project, but it will sometimes act as a staging ground for APIs that will later be incorporated into the Swift Standard Library. When that happens, such changes will be proposed to the Swift Standard Library using the established evolution process of the Swift project.
Swift Numerics uses GitHub issues to track bugs and features. We use pull requests for development.
Questions about how to use Swift Numerics modules, or issues that are not clearly bugs can be discussed in the "Swift Numerics" section of the Swift forums.
¹ Swift is currently unable to use the fully-qualified name for types when a type and module have the same name (discussion here: https://forums.swift.org/t/pitch-fully-qualified-name-syntax/28482). This would prevent users of Swift Numerics who don't need generic types from doing things such as:
import Complex // I know I only ever want Complex<Double>, so I shouldn't need the generic parameter. typealias Complex = Complex.Complex<Double> // This doesn't work, because name lookup fails.
For this reason, modules that would have this ambiguity are suffixed with
Module within Swift Numerics:
import ComplexModule // I know I only ever want Complex<Double>, so I shouldn't need the generic parameter. typealias Complex = ComplexModule.Complex<Double> // But I can still refer to the generic type by qualifying the name if I need it occasionally: let a = ComplexModule.Complex<Float>
Real module does not contain a
Real type, but does contain a
Users may want to define their own
Real type (and possibly re-export the
Real module)--that is why the suffix is also applied there.
New modules have to evaluate this decision carefully, but can err on the side of adding the suffix.
It's expected that most users will simply
import Numerics, so this isn't an issue for them.