Skip to content
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.

Sign up for GitHub

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

A better phrasing for generic methods. #3428

Merged
merged 3 commits into from
Dec 18, 2024
Merged

A better phrasing for generic methods. #3428

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f7abbfc
A better phrasing for generic methods.
TruscaPetre Nov 17, 2022
7982ad0
Merge `main` into `TruscaPetre:patch-1`
chriskrycho Dec 18, 2024
17e2dcb
Ch. 10.1: further clarify graf about methods in `impl<T> ...` blocks
chriskrycho Dec 18, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/ch10-01-syntax.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -216,8 +216,8 @@ generic type after `impl`, Rust can identify that the type in the angle
brackets in `Point` is a generic type rather than a concrete type. We could
have chosen a different name for this generic parameter than the generic
parameter declared in the struct definition, but using the same name is
conventional. Methods written within an `impl` that declares the generic type
will be defined on any instance of the type, no matter what concrete type ends
conventional. If there is a method written within an `impl` that declares the generic type,
that method will be defined on any instance of the type, no matter what concrete type ends
up substituting for the generic type.

We can also specify constraints on generic types when defining methods on the
Expand Down