Skip to content

depimpulation of pimpulous pimposity #487

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

Merged
merged 1 commit into from
Jan 14, 2016
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion tutorials/FAQ/chaining-implicits.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ partof: FAQ
num: 6
---

The pimp my library pattern allows one to seemingly add a method to a class by
The enrich-my-library pattern allows one to seemingly add a method to a class by
making available an implicit conversion from that class to one that implements
the method.

Expand Down
2 changes: 1 addition & 1 deletion tutorials/FAQ/context-and-view-bounds.md
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ useful for context bounds:
What are View Bounds used for?
------------------------------

View bounds are used mostly to take advantage of the _pimp my library_ pattern,
View bounds are used mostly to take advantage of the _enrich my library_ pattern,
through which one "adds" methods to an existing class, in situations where you
want to return the original type somehow. If you do not need to return that
type in any way, then you do not need a view bound.
Expand Down
2 changes: 1 addition & 1 deletion tutorials/scala-for-csharp-programmers.disabled.html
Original file line number Diff line number Diff line change
Expand Up @@ -955,7 +955,7 @@
}
}

Well, big deal. Scala can pimp existing types with new methods just like
Well, big deal. Scala can enrich existing types with new methods just like
C#, but using a different syntax. In related news, Lisp uses a different
kind of bracket: film at eleven. Why should we be interested in Scala
implicits if they’re just another take on extension methods?
Expand Down