Brooklyn Zelenka

Bring in line with latest community standards

1

Credo now warns by default on use of `Apply.apply`, and piping into anonymous functions. We should consider making these not conflict out of the box. > {Credo.Check.Readability.PipeIntoAnonymousFunctions, false}, > #...

- [x] `Bifunctor` - [ ] `Multifunctor` - [ ] `Contravariant` - [x] Comonad - [ ] `Plus` - [ ] `Alt` - [ ] `Alternative` - [ ] `MonadPlus`...

Seems to be somewhere around `Chain` or `Monad`. Almost certainly long operation in a prop check.

Applicative do notation

4

What it says in the title

Arrow do notation

1

What it says in the title

Continuation passing style would be a nice addition for many use cases

@curryspec & @partialspec

1

The `@spec` equivalents of `defcurry` and `defpartial`

Add multiple anon function arities in defpartial

5

Current behaviour for `defpartial` is to give multiple options for the first invocation, but then you have to apply single arguments after that. It should return anonymous functions with multiple...

Pointfree

1

Allow point free function definitions

The README should be fleshed out more, especially with reasoning behind why this library could be useful, and what it supports (ex. Witchcraft & Algae)