Bay area peeps -- we're hosting an East Bay #rustlang meetup on the 18th! Come join us in downtown Oakland, steps away from BART :)
Remote
rain 🌦️
@rain@hachyderm.io
mastodon 4.7.3(gender)queer transsexual, atheist and scientific humanist, rust person 🦀 and eng @oxidecomputer@hachyderm.io with computer opinions.
they/them (she ok), content under CC BY 4.0
2204 Followers
347 Following
20 Posts
Joined November 14, 2022
website:
github:
cargo-nextest:
Published the design document for how nextest implements records, replays and reruns. It's very large — over 6000 words! Lots of decisions and alternatives considered, to make what I believe is the best implementation of this set of features in the industry. Have a look!
We're hosting a Rust meetup in SF, WEDNESDAY April 15. Join us!
Released cargo-nextest 0.9.117 with experimental support for running benchmarks from within nextest, via `cargo nextest bench`.
Why use this instead of cargo bench? In case you want to benefit from nextest's features, such as per-test isolation, setup scripts, or wrapper scripts.
Call for testing: nextest can now rerun failing tests!
cargo nextest self update --version 0.9.123-b.3
# enable functionality, see link
cargo nextest run
If tests fail and/or the run is cancelled, then:
cargo nextest run -R latest
to rebuild and pick up from where the test run left off.
Please test this out!
https://nexte.st/docs/features/record-replay-rerun/
A lot of care went into building replay/rerun functionality in a way that's robust, both in the architecture and in the UX, and I'm excited about your feedback.
Replying to
Replying to
Read more about how the RustRover IDE supports nextest:
https://blog.jetbrains.com/rust/2026/04/03/rustrover-2026-1-professional-testing-with-native-cargo-nextest-integration/
Call for testing: cargo nextest 0.9.119-b.2 with pager (like less) support!
Please run `cargo nextest self update --version 0.9.119-b.2`, then try out:
cargo nextest list
cargo nextest show-config test-groups
cargo nextest (without further arguments)
cargo nextest run -h and --help
Thanks!
EDIT: Please update to beta 2 for a bugfix, thanks :)
Replying to
@anselmschueler@ieji.de yep! https://docs.rs/iddqd/latest/iddqd/macro.id_upcast.html
Ideally I'd be able to put a covariance bound on the trait's associated type itself, but there's no way to do that in stable Rust
Replying to
@argv_minus_one@mastodon.sdf.org Definitely something I considered, but the API got too unwieldy, it's already complex enough. You can use a newtype though!
Replying to
@slatian@pleroma.envs.net To add to this, especially the bi/trijective maps creep into database constraint territory. In theory you could use this pattern for pretty arbitrary sets of constraints. I want to keep it simple and useful though
Replying to
@hermitcl@aus.social Someone asked on Reddit if it was named after the former Overwatch player 😬