-
Notifications
You must be signed in to change notification settings - Fork 15
Change to attr format? #48
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
Comments
Edit to avoid notifying others: Yes. |
Thanks, @Enselic. To be sure I understand, this is an active topic of discussion? Is that the right conclusion? |
Yep! See https://github.com/rust-lang/rustdoc-types/blob/trunk/CHANGELOG.md#v0.36.0
Also yep! See rust-lang/rust#137645 and https://github.com/rust-lang/rust/pull/138063/files#r1981637128 for example |
I'm gonna close this as not being a question/tracked elsewhere. |
Thanks, @aDotInTheVoid. I should have thought to check the changelog. 🤦 |
In JSON produced by recent versions of rustdoc-types, the attrs look like this:
I think they used to more closely resemble what appears in the source code:
Can I just confirm the change is intentional?
Not to nit, but the
falseimplied_by
as one word looks suspicious.The text was updated successfully, but these errors were encountered: