rust-unofficial/patterns

Clarify paragraph in Generics as Type Classes

Open

#337 opened on Jan 6, 2023

View on GitHub
 (0 comments) (1 reaction) (0 assignees)Shell (6,622 stars) (292 forks)batch import
A-functionalC-clarificationgood first issue

Description

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!

Contributor guide

Tech stack
rust
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rust genericstype classes concept
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85
Research direction
Examine the paragraph at https://rust unofficial.github.io/patterns/functional/generics type classes.html. Rewrite the second sentence to clarify the contrast between class inheritance and type classes. Look for the source file likely in patterns/src/functional/generics type classes.md in the repository.