-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Rustdoc-Json: Add Path
type for traits.
#100335
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
I can review the JSON conversion change at least. |
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.
The changes to json/conversions.rs
and rustdoc-json-types
look good to me. I left a few comments. I'll let Guillaume or someone else review the changes to the tests and testing infrastructure since I'm not familiar with it.
name: String, | ||
id: Id, | ||
args: Option<Box<GenericArgs>>, | ||
param_names: Vec<GenericBound>, |
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.
IIUC, you removed this field because it was always empty?
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.
Yeah, is was origionaly ment to be part of handling dyn
traits, but was never used, and we handle dyn differently now (#99787)
Since you updated |
73ac9ca
to
86bdb3e
Compare
Bumped format version (interesting that highfive didn't send a message about this), fixed comments |
We should add a check for that, indeed. |
Would be better to directly put it into the CI instead. Like that it cannot be mistakenly forgotten. |
How would you do that? Something like https://github.com/obi1kenobi/cargo-semver-check? |
No, something much simpler. I'll send a PR. |
Just realized that what I had in mind would fit without a real semver check. So we do need something like the crate you provided. |
Looks good to me, thanks! @bors r+ |
We can now check for semver regressions with github-actions using |
…=GuillaumeGomez Rustdoc-Json: Add `Path` type for traits. Avoids using `Type` for trait fields, as a trait must always be a path, and not any other kind of type. `@rustbot` modify labels: +A-rustdoc-json +T-rustdoc Closes rust-lang#100106
…mpiler-errors Rollup of 8 pull requests Successful merges: - rust-lang#99646 (Only point out a single function parameter if we have a single arg incompatibility) - rust-lang#100299 (make `clean::Item::span` return `Option` instead of dummy span) - rust-lang#100335 (Rustdoc-Json: Add `Path` type for traits.) - rust-lang#100367 (Suggest the path separator when a dot is used on a trait) - rust-lang#100431 (Enum variant ctor inherits the stability of the enum variant) - rust-lang#100446 (Suggest removing a semicolon after impl/trait items) - rust-lang#100468 (Use an extensionless `x` script for non-Windows) - rust-lang#100479 (Argument type error improvements) Failed merges: - rust-lang#100483 (Point to generic or arg if it's the self type of unsatisfied projection predicate) r? `@ghost` `@rustbot` modify labels: rollup
Asked about this on zulip: Turns out these days the mention won't fire if the author in in the CC list, which isn't ideal |
Avoids using
Type
for trait fields, as a trait must always be a path, and not any other kind of type.@rustbot modify labels: +A-rustdoc-json +T-rustdoc
Closes #100106