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

Document frunk_core dependency requirement for [Labelled]Generic #219

Merged
merged 1 commit into from
Jul 4, 2023
Merged

Document frunk_core dependency requirement for [Labelled]Generic #219

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
9 changes: 9 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -162,6 +162,15 @@ assert_eq!(remainder, hlist![true]);
`Generic` is a way of representing a type in ... a generic way. By coding around `Generic`, you can to write functions
that abstract over types and arity, but still have the ability to recover your original type afterwards. This can be a fairly powerful thing.

#### Setup

In order to derive the trait `Generic` (or `LabelledGeneric`) you will have to add `frunk_core` dependency

```toml
[dependencies]
frunk_core = { version = "$version" }
```

Frunk comes out of the box with a nice custom `Generic` derivation so that boilerplate is kept to a minimum.

Here are some examples:
Expand Down