kennytm

This sounds like a very bad workaround. Wouldn't it be easier just create the Nix formula?

Thanks for the report. Which OS are you using, and are the cargo-kcov version between 09-06 and 10-01 the same?

Thanks. > I haven't checked any compiles between 09-06 and 10-01 I mean the version of `cargo-kcov` itself, not the compiler 😅

Thanks. The range https://github.com/rust-lang/rust/compare/90d36fb59...2ab3eba30 contains quite many PRs, but I think it's caused by cargo-kcov not updated to properly handle rust-lang/rust#53829.

@marco-c Thanks, but > GCC 4.9 or higher is required. Unless it is independent of the C compilers, nope.

@marco-c I thought it means GCC needs to be installed? Also I saw the `build.rs` which references `llvm-config` that does not exist in $PATH of macOS. ---- Anyway this project...

with #2920 you could also write ```rust match x { const { CONST } => { }, _ => { }, } ``` furthermore, because of rust-lang/rust#65490, it is _not_...

if we follow the roadmap in https://github.com/rust-lang/rfcs/issues/263#issuecomment-427629005 treating `@` as pattern intersection, `_ @ CONST` would naturally be supported **but** not having the effect OP desired (if you forget to...

One thing I'm uneasy with reusing the [`object-provider` API](https://docs.rs/object-provider/0.1.0/object_provider/) is the double lifetime: ```rust fn get_context(&'a self, request: Request) -> ProvideResult { ... } ``` Having one explicit lifetime can...

@yaahc > I do feel it is important to keep the explicit type parameter rather than manually doing the type id comparisons, assuming that's what you mean here. I agree...