Rain
Seems like the better way to do it, and depending on how things go we may also want to make it the default. From @jclulow: > I think contracts is...
I've been playing around with `target-lexicon` a bit and it seems like while most of the time it is pretty faithful to the rustc target json, some of the time...
These limit the number of concurrently running *futures*, which often but doesn't always limit overall concurrency. Add a note about this. From @hawkw: > if your stream is returning `tokio::spawn(do_stuff())`...
Do the checklist before filing an issue: * [x] Is this related to the actions-rs Actions? If not, use GitHub Community forum to ask questions about Actions in a whole:...
With something like a typed UUID format, there are several things to consider: 1. The types within Rust code 2. The serde serialization format used for our external APIs 3....
Our current model is what I'd refer to as the "marker model": ```rust struct TypedUuid { uuid: Uuid, marker: PhantomData, } ``` One kind of type that isn't representable in...
Related: - #1525 - #1526 Similar to #1526, we'd like a machine-readable way for configuration output to be presented. Some thoughts: - Probably want options on the `nextest show-config` UI....
Related: - #1525 - #1526 Users should have a way to tell what settings their tests are running with, and what the overall nextest configuration is. We have some basic...
Nextest has a number of sources of configuration: * repository-specific configs * probably user-specific configur * CLI and environment parameters * profiles and per-test overrides As the complexity of configuration...
With cargo-nextest 0.9.71, we now include libstd unconditionally in archives. This is done for two reasons: * proc-macro tests * `-C prefer-dynamic` As of Rust 1.78, this makes archives: *...