David Barsky
David Barsky
Hi! This PR introduces a few of the things I've talked about in #287, namely: - [x] Compile on the 2018 Edition - [x] Rename `#[derive(Fail)]` to`#[derive(Error)]` - [x] Rename...
## 💡 Feature description Hi! I wanted to see if you'd be interested in a PR that supports serializing all non-hash or sort key fields serialized as a string or...
Stacked atop of #2790.
## Bug Report ### Version ```bash coverage-repro on master is 📦 v0.1.0 via 🦀 v1.62.0-nightly ❯ cargo tree coverage-repro v0.1.0 (/Users/dbarsky/Developer/coverage-repro) └── tracing v0.1.34 ├── cfg-if v1.0.0 ├── pin-project-lite...
## Feature Request ### Motivation A decently common feature request that comes up in conversations is for tracing to provide some sort of visualization of spans and events in some...
We missed this change, which, whoops.
While researching tracing ecosystem, I found a lot of similar typos. Here are some of them: - https://docs.rs/tracing/0.1.40/tracing/attr.instrument.html (in addition to already mentioned `std::fmt::Debug` problem, this page contains similarly broken...
At work, some of the indexing would take up the entire status bar because of `buck-out` has some *pretty* long paths. This is an option to make it less chatty/loud.
Resolves https://github.com/rust-lang/rust-analyzer/issues/15892. This PR, as structured, adds runnable support to `rust-project.json`-based workspaces, and that works pretty nicely. It's not as polished as I'd like it to be (namely: interpolation of...
Hi! I'm a `tracing` maintainer. Overall, I'm really excited to see people working in this space! I have a few disorganized thoughts: - Congrats on creating a new tracing/instrumentation library!...