Wojciech Polak
Wojciech Polak
So, #411 is closed now, which I guess was a blocker.
I thought about it. In my opinion yes, there should be a way to retrieve test case name, however right now I'm not sure how to achieve it without creating...
I thought either to "hide it" inside some macro like `test_case_name!()` (similar to `module_path!()` ) and then let `#[test_case(...)]` parse function body and replace `test_case_name!()` Another idea is to have...
Okay, I feel macro may be quite cumbersome to achieve. However, I was thinking a bit about the issue and what about something like this: ```rust #[test_case("".into(), 0)] #[test_case("bar".into(), 1)]...
Hmm okay, but I think I can simply modify this idea with `TestCase` as a struct and go further with macros: ```rust #[test_case("".into(), 0)] #[test_case("bar".into(), 1)] fn foo(arg_1: String, arg_2:...
Okay, I have some extra notes and edge cases we need to consider but for now, it seems to be a good way forward. It requires major refactoring in macro...
I think this is the same story: There is one case where I find relying on `rustup` excessive: `cargo-dylint --help` fails with exit code 1 if there is no `RUST_TOOLCHAIN`...
My apologies, I made a mistake - it's not a `cargo-dylint` but `dylint-link` that exits with code 1: