slatec-src
no_std implementation-provider selection and native link integration for
slatec-rs. Applications that need an implementation provider use this crate;
declaration-only users can depend on slatec-sys directly.
bundled is the canonical ordinary-provider feature. Its target-specific
carrier contains one hash-verified accepted-source archive for
x86_64-pc-windows-gnu and x86_64-unknown-linux-gnu, providing special-elementary,
special-gamma, special-beta, special-error, special-integrals,
special-polynomials, special-airy, special-bessel,
special-scalar-expanded, and roots-scalar. It links without a
compiler, source cache, system directory, or network access. Every other
family is independently provenance-blocked and fails before touching those
inputs. source-build consumes a separately acquired, checksum-verified cache
and never accesses the network. system links an explicitly located archive,
while external-backend emits no link directives.
For the supported GNU MinGW source backend, every selected original Fortran
source is compiled separately and retained as a separate member in a normal
static archive. No partial link, generated amalgamation, or whole-archive link
is used. A broad family can therefore produce a large intermediate archive
while a final executable extracts only referenced member closures. This is
measured by the deterministic reports under generated/native-link/; an
external or system provider is not assumed to share those properties. See
docs/architecture/native-link-granularity.md.
Safe-wrapper module layout is audited separately and does not modify this
provider's one-source-per-object archive construction; see
docs/architecture/safe-facade-link-granularity.md.
This crate owns the workspace's Cargo links = "slatec" namespace. It never
downloads source during a build. The strongest validated source-build profile
is GNU MinGW 14.2 on x86_64-pc-windows-gnu and GNU Fortran 11.4 on
x86_64-unknown-linux-gnu; system and external backends must supply an
independently compatible ABI. Packages contain closure metadata and the
reviewed machine-constant overrides, not the separately acquired source cache.