-
Notifications
You must be signed in to change notification settings - Fork 13.3k
start properly testing attributes in positions #140948
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
base: master
Are you sure you want to change the base?
Conversation
r? @wesleywiser rustbot has assigned @wesleywiser. Use |
r? jieyouxu |
Oh, this is great! I was just recently working on this, but happy to have someone actually make it happen. I look forward to this being accepted. Let me know if you want any help. I think there are a few tests that could eventually get deleted once everything gets covered. For example:
Some suggestions:
|
cc @jdonszelmann (as you may want to co-review) |
Yes, I'd like that. might take a little because of rust week @rustbot claim |
I think we also ought to test combinations of attributes. Such as #[ATTRIBUTE]
#[naked]
extern "C" fn naked(){} Are there more like that?
Just added another commit with these. I originally had them..not sure where they went... |
Just these couple of edits have already been quite annoying and error prone. Doing this for dozens of attributes is going to be untenable in the long run. This needs to be automatically generated, and I have some ideas about how to do that. |
See the readme for the motivation. Just doing three attributes for now to get feedback on the overall implementation and direction.
Please let me know if there are additional positions that need testing!