Skip to content
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

Switching to toml_edit broke my tests because of sirens in the distance (macrotest) #123

Closed
ijackson opened this issue Mar 5, 2025 · 1 comment

Comments

@ijackson
Copy link
Contributor

ijackson commented Mar 5, 2025

Firstly, apologies for filing this ticket here. None of this is the fault of macrotest. IDK what you might want to do about it. But, it took me considerable digging to discover the problem, so I though I should report it here because it was cargo update -p macrotest that triggered the problem. Someone else this happens to might find this ticket, even if it's closed by then.

I have a crate where I use macrotest for testing. macrotest uses toml_edit. toml_edit has an ill-advised API which induced a bug in proc_macro_crate, such that proc_macro_crate doesn't work when Cargo.toml declares the dependencies with syntax like this:

dependencies = { .... }

Humans rarely write like this, but since d551fbf "Use toml_edit instead of basic-toml (#119)", macrotest does. (My git bisect fingered that commit.)

The fact that this happened because macrotest changed to toml_edit, triggering a bug in proc_macro_crate's use of toml_edit again, seems to be coincidence.

OTOH if you feel like this decreases your confidence in toml_edit you might choose to switch horses (toml libraries) again.

Thanks for your attention.

@ijackson ijackson changed the title Switching to toml_edfit broke my tests because of sirens in the distance (macrotest) Switching to toml_edit broke my tests because of sirens in the distance (macrotest) Mar 5, 2025
@taiki-e
Copy link
Collaborator

taiki-e commented Mar 8, 2025

It seems proc-macro-crate bug has been fixed.

@taiki-e taiki-e closed this as completed Mar 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants