Skip to content

Chapter 12.3: unhelpful reference to judgmental terms #2863

@jruderman

Description

@jruderman
  • I have checked the latest main branch to see if this has already been fixed
  • I have searched existing issues and pull requests for duplicates

URL to the section(s) of the book with this problem:

https://doc.rust-lang.org/book/ch12-03-improving-error-handling-and-modularity.html

Note: Using primitive values when a complex type would be more appropriate is an anti-pattern known as primitive obsession.

Description of the problem:

These are judgmental terms that contradict the overall tone and message of the book. Googling this phrase does not lead to practical advice about when to create domain-specific types in Rust, but does raise the emotional stakes by revealing equally judgmental jargon that some programmers use when arguing against creating new types.

Suggested fix:

Remove the quoted sentence.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions