-
Notifications
You must be signed in to change notification settings - Fork 152
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
Get rid of proc-macro-error
(RUSTSEC-2024-0370 and syn
version)
#351
Comments
There is also |
proc-macro-error is unmaintained of now. The authors of the validator crate are aware of the issue and working on it (Keats/validator#351) as of now, however, there is no solution. As this issue is not critical for operation we ignore it for now and update the affected dependencies when the updates are available.
Update on this in case anyone is following: PR has been merged, awaiting new version release though. |
Just to set expectations, is there an ETA on a release? We have a low-urgency ticket to resolve the RUSTSEC issue in our repo, so it would be helpful if I could update that with a timeframe. Thanks for all the work that goes into maintaining this crate, it's much appreciated 🙏 |
Probably next week when i get back from holiday |
So, someone filed an advisory against
proc-macro-error
for being unmaintained. Sincevalidator-derive
uses it, usingvalidator
made this show up in our CI. Tbh I'm somewhat sceptical as to the proposed solution of migrating toproc-macro-error-2
, both because it is very recent and already had to release a bugfix for an oversight they made when forking the project, and because the primary reason to useproc-macro-error
at all (to me, at least) is because it abstracts over stable vs. nightly diagnostic capabilities for proc macros, which the sequel doesn't do - they use a feature flag instead that needs to be set by the dependent.That said, the original
proc-macro-error
due to its age is also one of the few crates in our dependency graph to still depend onsyn
version 1. Having to compilesyn
twice in an early stage of the build (since it is needed for basically all proc macros) is not great, and might honestly be a better / bigger reason to stop usingproc-macro-error
. As an alternative to switching toproc-macro-error2
, here's a recent PR inutoipa
(in particular theDiagnostics
bit here, which GitHub likes to collapse by default). It's a bigger PR, but their macro API surface is also very large, so it should be less effort to do forvalidator-derive
if that is wanted.The text was updated successfully, but these errors were encountered: