Bug: Running multiple expansion tests may interfere with each other

[Emoun]

Bug: Running multiple expansion tests may interfere with each other

[Emoun]

@eupn Yep, can confirm #45 fixes this bug.

Thanks for the quick response to this issue and the quick fix.

[eupn]

@Emoun a new version 1.0.3 was published on crates.io.

[eupn]

@Emoun

Hello and thank you for this report!

The macrotest crate is most likely the reason because it creates a temporary cargo crate for each "set" of expansion tests and those crates (or their names/paths) are happened to be non-unique thus causing the interference. One possible solution to this might be to create temporary crates with randomized name&path to make them unique for each "set" of expansion tests thus eliminating the interference.

This solution should be implemented internally in order to support your use-case.

[Emoun]

@eupn thanks for the clarification, I was quite confused about what no bin target referred to.

If you would like me to help you test a potential fix you implement just @ me and I'll try to run it on my use case.

[eupn]

@Emoun feel free to pull this branch (via git dependency in cargo) and run against your project: #45.

As soon as this PR gets merged I'll publish a new version (v1.0.3) on crates.io.