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.

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

fix(book): Correct type parameter naming convention to pascal case #79

Merged
merged 2 commits into from
Jun 1, 2024

Conversation

felixpherry
Copy link
Contributor

The book previously recommended using camel case for type parameter names

@c-git
Copy link
Contributor

c-git commented Jun 1, 2024

Actually camel case is correct. Rust uses different conventions for different items see https://rust-lang.github.io/api-guidelines/naming.html

@LukeMathWalker
Copy link
Collaborator

The correct wording is "upper camel case", as stated in the page you linked @c-git. Thanks for pointing out the imprecision @felixpherry!

@LukeMathWalker LukeMathWalker merged commit e99a153 into mainmatter:main Jun 1, 2024
2 checks passed
hongyanca pushed a commit to hongyanca/100-exercises-to-learn-rust that referenced this pull request Jun 1, 2024
…ainmatter#79)

* fix(book): Correct type parameter naming convention to pascal case

* Update book/src/04_traits/05_trait_bounds.md

---------

Co-authored-by: Felix Pherry <[email protected]>
Co-authored-by: Luca Palmieri <[email protected]>
felixpherry added a commit to felixpherry/100-exercises-to-learn-rust that referenced this pull request Jun 5, 2024
…ainmatter#79) (#1)

* fix(book): Correct type parameter naming convention to pascal case

* Update book/src/04_traits/05_trait_bounds.md

---------

Co-authored-by: Felix Pherry <[email protected]>
Co-authored-by: Luca Palmieri <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants