rustdoc: normalise type/field names - #128667
Merged
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Updates #100961
Import->Use, to better reflect the terminology of Rust & its syntaxTypeBinding->AssocItemConstraint, to sync up withcleanFnDecl->FunctionSignature, because that's what it isHeader->FunctionHeader, becauseHeaderis a very word that's very heavily loaded with different meaningsItemEnum::AssocType:default->type, because those items appear inimplblocks as well, where they're not the "default"ItemEnum::AssocConst:default->value, see the previous pointForeignType->ExternType, because "foreign" is not the right word thereasync->is_asyncThe docs of
ItemEnum::AssocType::type_& ofItemEnum::AssocConst::valueare also updated to be up to date with the clarification of the name of the fields