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

Fix link to the article: "Haskell Antipattern: Existential Typeclass" #254

Merged
merged 1 commit into from
Feb 4, 2023
Merged

Fix link to the article: "Haskell Antipattern: Existential Typeclass" #254

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 docs/design-decisions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,7 @@ Because of the first reason, there were not advantages by using typeclasses
compared to using records. This situation of wrapping a typeclass in an
existential is referred to as _"Existential Typeclass Anti Pattern"_. For
example,
[here](https://lukepalmer.wordpress.com/2010/01/24/haskell-antipattern-existential-typeclass).
[here](https://web.archive.org/web/20201109041924/http://lukepalmer.wordpress.com/2010/01/24/haskell-antipattern-existential-typeclass/).

## Why do you use lawless typeclasses for combinators?

Expand Down