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

Jump to bottom

Clarify paragraph in Generics as Type Classes #337

Open
alensiljak opened this issue Jan 6, 2023 · 0 comments
Open

Clarify paragraph in Generics as Type Classes #337

alensiljak opened this issue Jan 6, 2023 · 0 comments
Labels
A-functional Area: Content about Functional Programming C-clarification Category: Content that clarifies existing content good first issue Good for newcomers

Comments

@alensiljak
Copy link

The section 5.2. Generics as Type Classes contains the following paragraph:

In object-oriented languages, classes can inherit behavior from their parents. However, this allows the attachment of not only additional behavior to particular members of a type class, but extra behavior as well.

which I find fairly confusing. The second sentence contains repetitive words and does not clarify the first statement enough. It would help if this paragraph was rewritten and/or expanded to add meaning and additional information.
Thanks!
@simonsan simonsan added the C-clarification Category: Content that clarifies existing content label Jan 6, 2023
@simonsan simonsan added good first issue Good for newcomers A-functional Area: Content about Functional Programming labels Apr 8, 2023
@simonsan simonsan changed the title Clarify paragraph in 5.2 Clarify paragraph in Generics as Type Classes Apr 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-functional Area: Content about Functional Programming C-clarification Category: Content that clarifies existing content good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alensiljak @simonsan