Skip to content

Commit

Permalink
readme: more detail, changes from refined
Browse files Browse the repository at this point in the history
  • Loading branch information
raehik committed Oct 24, 2024
1 parent 43c3c5f commit 5e0a616
Showing 1 changed file with 58 additions and 13 deletions.
71 changes: 58 additions & 13 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,10 @@ Rewrite of Nikita Volkov's [refined][refined-nv-hackage] library.

* same concept
* same performance
* more instances
* more predicates (signed value comparisons)
* more features (functor predicates, predicate simplification)
* better ergonomics (no insidious `Typeable` constraints)
* internals: fewer dependencies (no `aeson`), better errors, more concise
* neater internals: fewer dependencies (no `aeson`), better errors, more concise

## Why?
I used the original [refined][refined-nv-hackage] library fairly extensively to
Expand All @@ -23,28 +24,65 @@ years. A good excuse to rewrite from the ground up.

All source code is original.

## Major changes from original refined
### Simplified errors
### Why not merge into refined?
rerefined is a complete modern rewrite. As such, it works plenty differently,
and doesn't support older GHCs.

I do want to add missing features into refined, such as functor predicates. But
refined is receiving minimal maintenance recently (2022-2024), and my changesets
are languishing.

## Differences from original refined
### New features
#### `Refined1` for functor predicates
[refined-gh-refined1]: https://github.com/nikita-volkov/refined/pull/99

Some predicates operate on the `f` of an `f a`. In such cases, given an
`Refined1 (f a) :: Refined1 p f a`, we should be permitted to make changes
inside the functor, that do not change the functor structure/shape. These are
provided by the `Functor` and `Traversable` instances on `Refined1`.

Draft PR for refined at [refined#99][refined-gh-refined1].

#### Type-level refinement simplification
A primitive predicate simplifier is provided at `Rerefined.Simplify`. It can
simplify immediate cases of identity laws and so on.

#### Infix operator-style predicate definitions
`Rerefined.Predicate.Operators` exports type synonyms for writing predicates
using infix operators. (refined provides a handful, but they coincide with
existing operators, such as `&&`.)

### Changes
#### Simplified errors
refined encoded the logical predicates in its error type. This doesn't enable
any further analysis, just turns a non-sum type into a sum type and complicates
consumption. Furthermore, this error type is first transformed into another
recursive ADT, which is then pretty printed. This is unnecessary (even mentioned
in the code).
recursive ADT, which is only then pretty printed. This is unnecessary (even
mentioned in the code).

rerefined has a single-constructor error type which can be easily and
efficiently turned into a string-like in a single pass.

### No insidious `Typeable` contexts
#### No insidious `Typeable` contexts
[hackage-tls]: https://hackage.haskell.org/package/type-level-show

See [refined#101](https://github.com/nikita-volkov/refined/issues/101).
`Typeable` is useful, but the way it is used brings lots of `Typeable` contexts.

rerefined asks that you do a bit more work upfront, but gives you tools and
grants much more power. Predicates declare their "predicate name" explicitly as
a type-level `Symbol`. Precedence is supported and infix operators are welcomed.
(For now, the logical operators primarily look like their propositional logic
counterparts.)
grants much more power. Predicates now must declare a "name":

```haskell
class Predicate p where type PredicateName (d :: Natural) p :: Symbol
```

Precedence is supported to permit writing names as infix operators. (For now,
the logical operators primarily look like their propositional logic
counterparts.) The [type-level-show][hackage-tls] package provides utilities for
printing `Natural`s and handling precedence.

### Cleaner design
#### More re-use
What do `LessThan`, `GreaterThan`, `EqualTo` etc. have in common? They're all
relational binary operators where one value is a pre-filled `Natural`. rerefined
packs all of these into a single predicate that takes a type-level relational
Expand All @@ -59,7 +97,7 @@ define length comparisons, where the other value is taken from the input's
length (rather than its numeric value). This does not take a sign, since length
must be non-negative.

### More instances
#### More instances
You know that length comparison predicate above? It has a _single instance_ for
each of `Refined1` and `Refined`:

Expand All @@ -81,5 +119,12 @@ We get a ton more instances for a ton less code. (Note that mono-foldable has a
surprisingly small footprint, as most of its transitive dependencies are core
libraries.)

### Other
* much cleaner module organization
* predicates defined in standalone modules; only import what you need
* `Rerefined.Predicate.Via.validateVia` for defining predicates that are
implemented by an existing predicate
* more logical predicates (NAND, if, if-and-only-if)

## License
Provided under the MIT license. See `LICENSE` for license text.

0 comments on commit 5e0a616

Please sign in to comment.