Heath Stewart
Heath Stewart
We were on `fe2o3-amqp` (and dependencies) version 0.12 so we'll have to migrate some of our code first; however, seems like it would solve the issue and get rid of...
To summarize, our problem is in duplicate dependencies on `getrandom`, which 0.2 is a transitive dependency as well and the [WASM support](https://docs.rs/getrandom/latest/getrandom/#webassembly-support) workarounds are incompatible between 0.2 and 0.3, as...
Another use case we have is to record the `rustc` version used to compile with our library that we telemeter, if enabled. Currently I don't see anything obvious recorded in...
Interesting. I ran `readelf -a ` and it didn't dump the `.comment` section, but doing what you did explicitly worked. Maybe `std` could expose that if there's enough demand. As...
Disabling colored output requires convoluted `cargo test --color=never -- --color=never` incantation
> There is already `RUST_TEST_THREADS`, so following the pattern would be `RUST_TEST_COLOR`, I suppose? `cargo build` already respects the `NO_COLOR` env var e.g. `NO_COLOR=1 cargo build` so could that be...
Disabling colored output requires convoluted `cargo test --color=never -- --color=never` incantation
Given [`NO_COLOR`](https://no-color.org/) is fairly ubiquitous, could `cargo` - especially once it handles all the rendering - document support for it? Env vars are handy when you want to control color...
That's correct. The generated GUID at initial design time is a critical design feature and was never really designed to be referenced. In fact, given how the new setup engine...
I was the architect of the VS setup engine and can best answer that. No, it hasn't changed. There's also no algorithm. As explained [above](https://github.com/microsoft/terminal/issues/19063#issuecomment-3029757234), it was intentionally random to...
Support for using `.editorconfig` files so that it adjusts tabs, spaces, etc. defined therein.