2025-08-30 –, FORGE (Room 1)
At least 1-2 times per week, accidental breaking changes sneak into the new release of some popular Rust package, despite the maintainers' best efforts.
Why is this still a problem 10 years after Rust 1.0?
What will it take to finally stop such breakage, so we can have fearless cargo update?
At least 1-2 times per week, accidental breaking changes sneak into the new release of some popular Rust package, despite the maintainers' best efforts. Much frustration usually follows!
How did we get here? Why is this still a problem after 10 years of stable Rust? Hasn't cargo-semver-checks solved this already? If not, what will it take?
Fearless cargo update is our goal — let's talk about how to make that happen!
Predrag has spent a decade working on query engines for almost every kind of data imaginable: from relational and graph databases to APIs and unstructured data files. He built Trustfall, a universal query engine that can query any data source(s), and cargo-semver-checks, a semantic versioning linter for Rust. He is the recipient of a Rust Foundation Fellowship for his work on cargo-semver-checks.
When not in front of a screen, Predrag enjoys skiing, ice hockey, and board games. He is also a huge space nerd. Ask him about the time he went to watch a giant rocket explode!