-
Notifications
You must be signed in to change notification settings - Fork 311
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
frozen-abi: Remove proc_macro_hygiene featurization #109
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #109 +/- ##
=========================================
- Coverage 81.8% 81.8% -0.1%
=========================================
Files 838 838
Lines 225941 225941
=========================================
- Hits 184945 184926 -19
- Misses 40996 41015 +19 |
// See https://github.com/solana-labs/solana/issues/11055 | ||
// We may be running the custom `rust-bpf-builder` toolchain, | ||
// which currently needs `#![feature(proc_macro_hygiene)]` to | ||
// be applied. | ||
println!("cargo:rustc-cfg=RUSTC_NEEDS_PROC_MACRO_HYGIENE"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems this originated at solana-labs#10905 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. thanks for tlc towards frozen-abi. :)
just curious, did you encounter some problems because of the remove d code?
No issue, I noticed it while reviewing solana-program/address-lookup-table#7 and wondered if it was still needed. Thanks for the review! |
Problem
There's still usage of an additional
proc_macro_hygiene
feature in frozen-abi and a few of its dependencies, but the issue referenced in the comment, solana-labs#11055, has been long resolved.Summary of Changes
I'm not sure if this is OK, but I wanted to get the discussion started with a simple PR to remove this usage everywhere. If I'm missing something, I'll be happy to close the PR!
Fixes #