Results 28 comments of Wojciech Polak

The procedural macro has no access to the TestInput structure. It would only have an identifier.

First of all, thank you for creating this issue. We are not using the built-in use of `test_case`. I will debug it today why the `parametric_test` is not working because...

https://github.com/synek317/test-case-derive/issues/1

Silly idea - what about line numbers :)?

That's an exciting idea. However, the intention was to provide a human-readable test description, not necessarily a compiler-readable one. For example: ``` #[test_case(4, 2 ; "when operands are swapped")] #[test_case(-2,...

Hmm in that particular case: Two tests cases with the same name would be translated to two functions with the same name. And that would cause an error, right? The...

I doubt that anyone is working on this. Feel free 😊 On Wed, Jan 24, 2024, 04:37 Augusto Fotino ***@***.***> wrote: > @luke-biel , is anyone working on this? >...

I know there is separate https://crates.io/crates/function_name crate that gives such a macro. I wonder if this will work as workaround or even inspiration for this issue solution

Ah yes, I made test by myself, you are right. Those two macros are incompatible :( I will think about the solution :)

Hi, does this feature depends on anything? I can't find any #73.