Skip to content

fix typos in README.md #1

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix typos in README.md #1

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
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,17 +2,17 @@

Experiment to declare typesclasses with programmatic type signatures.

## What's new with this encoding ?
## What's new with this encoding?

The main idea is to put the effort on implementing typeclasses, and then have data implementation for free, no typing required.
The magic lies in building the correct generic variants of the typeclass automatically (programmatically).

## How ?
## How?

All the magic is done thanks to:
- a new encoding that remembers the parameters variance of a Kind (covariant, contravariant, invariant).
- a lot of meta programming like in HOTScript to builds generics functions at compille time depending on kind instance (no need to declare exponentially many functions)
- a lot of meta programming like in HOTScript to builds generics functions at compile time depending on kind instance (no need to declare exponentially many functions)

Then we let this meta-compiler (typescript itself) build the correct generic types for the typeclass at compile time.

Knowning variance allows to know if we should `&` or `|` the generic types programatically and also know what are the default values (unknown for invariants and contravariants, and never for covariants).
Knowning variance allows to know if we should `&` or `|` the generic types programatically and also know what are the default values (unknown for invariants and contravariants, and never for covariants).