Repository navigation
base64-ng 2.1.0 #46
eldryoth
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
base64-ng 2.1.0 (Unreleased)
API and implementation freeze candidate. Publication, final native campaigns,
full-release CI and exact-source external acceptance are not complete.
Ordinary Throughput And Explicit Validation
WASM simd128 and exact Linux/SpacemiT X60 RVV validation remove the redundant
reference pass from eligible ordinary Auto decoding. Padding, canonical
tail bits, alphabet separation and exact diagnostics remain enforced.
DecodeValidation::ScalarReferenceretains the reference validation pass.It does not force scalar writing.
checked-backendindependently checksaccelerated validation and output, retaining quarantine and scalar recovery.
and formatting surfaces share the optimized routes without changing exact
lengths, reservation ordering or rollback contracts.
states, sync/Tokio adapters, Bytes updates and in-place decoding process
eligible bulk interiors while preserving progress and final-quantum rules.
draining the full queue fails; invalid tails do not trigger a drain.
Additive APIs
Base64Refbinds immutable borrowed input to validated codec settings andexact decoded length. Auto proofs may be reused; changed validator health
forces revalidation. Reference-policy views validate on every decode.
DecodeReportseparates requested validation, actual validator,writer, checked work and recovery. Static-token policy/report methods retain
canonical transactionality without replacing historical token methods.
surfaces. Bytes, Tokio, Serde, Multibase, PEM and OpenPGP expose opt-in
simd/checked-backendforwarding with unchanged defaults.removed. Existing incremental progress contracts remain the streaming API.
Compatibility And Limits
MSRV remains Rust 1.90.0; the active release compiler is 1.99.0.
The 13 Rust packages and supported npm loader target 2.1.0 together.
The core remains dependency-free. The 2.0.4 API/behavior baseline is retained.
Default features remain scalar; SIMD is opt-in. No SVE, broader RVV profile,
or new automatic AVX-512 decode route is admitted.
Secret/CT algorithms and protected-memory boundaries are unchanged. Ordinary
APIs are not constant-time or automatically wiping. Base64 is not encryption,
authentication or integrity protection. Enforce application input/output limits.
Canonical one-shot errors leave destinations unchanged; historical APIs keep
their documented mutation rules, and streams are not whole-message transactions.
The WASM loader rebuilds scalar and SIMD artifacts, with matching embedded
SHA-256 pins and build-generated source provenance. JavaScript signatures,
ownership, memory ceilings and hostile-input rejection contracts are unchanged.
Evidence And Upgrade Guide
Development paired measurements show material bulk improvements on named x86,
AWS ARM and Apple Silicon hosts, alongside small-input, checked-backend,
cold-start and malformed-input costs. They are not portable speed guarantees
or final release authorization. Read the policy decision
before interpreting the measurements.
See migration, the compiled
policy example,
freeze checklist and
release plan for final acceptance status.
This discussion was created from the release base64-ng 2.1.0.
All reactions