Rustdoc-Json: Store Variant Fields as their own item.#101462
Merged
bors merged 1 commit intorust-lang:masterfrom Sep 6, 2022
Merged
Rustdoc-Json: Store Variant Fields as their own item.#101462bors merged 1 commit intorust-lang:masterfrom
bors merged 1 commit intorust-lang:masterfrom
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #100587
Closes #92945
Successor to #100762
Unlike that one, we don't have merge
StructTypeandVariant, as after #101386Variantstores enum specific information (discriminant).Resolves the naming discussion (#100762 (comment)) by having seperate enums for struct and enum kinds
Resolves
#[doc(hidden)]on tuple structs (#100762 (comment)) by storing as aVec<Option<Id>>r? @GuillaumeGomez