Thore Goll

When you want to use the `gcovr_*` targets, another way could be to use the `--gcov-executable` option of `gcovr`: ```cmake include(CodeCoverage) if (CMAKE_CXX_COMPILER_ID STREQUAL "Clang") set(GCOVR_ADDITIONAL_ARGS --gcov-executable "llvm-cov gcov") endif()...

Is there now a way to mock a method returning `Option` without a `'static` lifetime? Could you give an example @asomers how one would approach this?

Thanks for the quick answer @asomers. This would probably work. A colleague of mine suggested another approach, by leaking a `Box` into a static reference: ```rust struct X; // dummy...

I would also be interested in this feature. Since the [tracking issue](https://github.com/rust-lang/rust/issues/85410) on `std` is entering its final comment period, how are the plans to port this to `async-std` as...

Main reason I went with this approach instead of the custom parsing of `cargo nextest list` is that I don't know how to correlate case positions back to attributes in...

I looked into this again and added the first approach (i.e. calling `cargo nextest list` and parsing the output to discover the test cases. This has other tradeoffs, though: -...

Thanks =) Sure, I'll have a look at the tests in the next days.

Hi @rouge8 I added tests for the new functionality. I also had to install `cargo nextool` now in the CI because the new tests require them when testing the `parameterized_test_discovery="cargo"`....

Hmm, can you give some more info please? 1. Which rust package are you testing? 2. What is your `neotest` config? 3. What is the output of `cargo nextest list...

Interesting, its seems like the test package name that [M._binary_path()](https://github.com/gollth/neotest-rust/blob/param/lua/neotest-rust/discovery.lua#L146) spits out is somehow unknown to cargo nextest, i.e. it is not part of `cargo nextest list ... | jq...