miniblog.

← Back to all posts
Jul 22, 2017 at 23:34
An elegant way of seeing if you're breaking API compatibility: try building all the downstream deps against WIP!
GitHub - brson/cargo-crusader: Test the downstream impact of Rust crate changes before publishing
GitHub - brson/cargo-crusader: Test the downstream impact of Rust crate changes before publishing
Test the downstream impact of Rust crate changes before publishing - brson/cargo-crusader

Related Posts

Oct 13, 2022 at 18:58
The different layers of the Nix ecosystem, and the overlay system to allow downstream users to override (c.f. dynamic binding):
Haskell for all: Stop calling everything "Nix"
May 20, 2019 at 21:49
Swift is exploring a cute idea for library transparency: you can distinguish between "this ABI is guaranteed to keep working" and "I want an extra layer of indirection so I can add to data structures without breaking downstream users". https://forums.swift.org/t/pitch-library-evolution-for-stable-abis/23026