TOOLING · Verified April 2026
Rust 1.85 and Go 1.26 in 2026:
tooling, versions, what changed.
Most ranking content cites Go 1.21/Rust 1.70. These are the current versions, with what actually matters in 2026.
RUST
1.85
Released February 2025. Stabilised the 2024 edition.
Key changes
- ✓ 2024 edition stabilised: updated reference rules, unsafe patterns, extern declarations
- ✓ use<..> syntax: explicit capture syntax in impl Trait, reduces lifetime confusion
- ✓ Strict provenance APIs: better unsafe code patterns for pointer operations
- ✓ expect() lint stabilised: enforces message quality in expect(msg) calls
- ✓ async closures: stable in 2024 edition (previously required nightly)
Source: blog.rust-lang.org/releases/ · Next: Rust 1.86 expected May 2025
GO
1.26
Released February 2026. Crypto and SIMD focus.
Key changes
- ✓ crypto/hpke: Hybrid Public Key Encryption (RFC 9180) in stdlib
- ✓ simd/archsimd: experimental SIMD package for vectorised operations
- ✓ Post-quantum hybrid KEM: X25519MLKEM768 for TLS 1.3
- ✓ PGO improvements: better inlining decisions with profiling data
- ✓ Generic type aliases: stable since 1.24 (Feb 2025), now widely used
Source: go.dev/doc/go1.26 · Go 1.27 expected August 2026
Cargo vs Go modules
| Feature | Cargo (Rust) | Go modules |
|---|---|---|
| Package manager | Cargo (built-in) | go mod (built-in since 1.11) |
| Registry | crates.io (centralized) | Module proxy (proxy.golang.org, decentralized) |
| Build from source | Always (compiles all deps) | Binary cache by default, source when needed |
| Build time impact | High: every dep compiled per project | Lower: module cache avoids recompile |
| Workspace support | cargo workspaces | go.work (multi-module workspaces) |
| Vendoring | cargo vendor | go mod vendor |
| Version resolution | Cargo.lock (per binary), exact reproducible | go.sum (checksums), go.mod semver |
Compile time reality: 10-60x slower for Rust
30-120s
Rust
Clean build, medium project (5-20k LOC with deps)
2-10s
Go
Clean build, equivalent project size
Incremental builds are faster (10-30s for Rust after a small change vs 1-3s for Go). But cold CI builds compound across a team. See cicdcalculator.com for what Rust's 30-120s compile times cost in CI at team scale.
IDE, formatter, and linter
IDE / LSP
Rust: rust-analyzer (VSCode, Neovim, Emacs) / RustRover (JetBrains, paid)
Go: gopls (all editors) / GoLand (JetBrains, paid)
Formatter
Rust: rustfmt: single canonical format, no debate
Go: gofmt: same philosophy. Go originated this.
Linter
Rust: clippy: catches hundreds of common mistakes, pedantic mode available
Go: golangci-lint: aggregates many linters, highly configurable
Test runner
Rust: cargo test (built-in) + Criterion for benchmarks
Go: go test (built-in) + testing package with benchmarks