-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for proc-macro crates #406
Comments
I don't think there's any positive reason, it's just not something that we recognize yet. It looks like this is from https://github.com/chesedo/despatma Looking at the code, it does seem to have tests that cargo-mutants could run, and code that it would understand. So this might be as simple as just changing the code in |
@chesedo it looks like the tests fail at head in despatma:
|
A newer Rust version recently changed some of the error messages. Can't quite remember if I updated the repo yet. I assume you are trying to test if |
If there is no solid, known reason then I can make a fork to test locally. And can make a PR if it works |
The linked branch here has a change to enable it, it just needs some manual
tests, and a test added to the tree!
…On Thu, Sep 12, 2024, 15:51 Pieter ***@***.***> wrote:
I don't think there's any positive reason
If there is no solid, known reason then I can make a fork to test locally.
And can make a PR if it works
—
Reply to this email directly, view it on GitHub
<#406 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACUR4YHZ3ABAONINXSGDDLZWHWCTAVCNFSM6AAAAABOCPMJDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBXGEYTKNZSGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Okay, I was able to manually test the linked branch and the mutants went from 16 to 49. I also fixed the repo if you also wanted to perform a manual test. |
OK yep this seems to work well on your crate:
|
Awesome! 🥳 Thanks for the update! |
- [x] Docs explaining that proc macro implementations can be mutated, but this only mutates the definitions and not the usage of macros - [x] News - [x] Maybe test that the testdata crate is fully covered? Fixes #406
I tried running
cargo-mutants
on aproc-macro
crate and was surprised to see it found no mutants. When I turned log level to tracing I saw this in the logs:Is there a reason
proc-macro
s are skipped that I might be missing?The text was updated successfully, but these errors were encountered: