Miles Frain

What if this the recipe was framed as "How to decode objects"? * If we know what fields to expect: Decode to record. * If fields are unknown: Decode to...

I'm thinking the JSON decoding examples should just be from hardcoded strings, or perhaps strings generated over FFI from `JSON.stringify`. I've had issue in the past with API demo service...

I'm a fan of [argonaut-codecs](https://github.com/purescript-contrib/purescript-argonaut-codecs). Haven't tried out [codec-argonaut](https://github.com/garyb/purescript-codec-argonaut) yet, but that also has appeal. Not sure what you meant by `codecs`. Would be great if their names were more...

Should we change `f` to `x` in the docs for the Annihilation law? ``` Distributivity: (f g) x == (f x) (g x) Annihilation: empty f = empty

Thanks for digging into this. --------- > Are you looking to implement these functions specifically for `NonEmptyList`? Or for `NonEmpty a f` in general? Planning on implementing specifically for `NonEmptyList`....

Here's a patched API proposal: **Instances:** ``` ----- Basic NonEmpty Lazy LazyNonEmpty (all) ----- Alt Applicative Apply Bind Eq Eq1 Extend Foldable FoldableWithIndex Functor FunctorWithIndex Monad Ord Ord1 Semigroup Show...

This also makes it easier to eventually add a CI watcher, like Travis or AppVeyor.

All of our libraries should have guides (along with better examples). Here are some of my favorites that set a bar to strive for: * https://github.com/purescript-contrib/purescript-argonaut-codecs/blob/main/docs/README.md * https://github.com/purescript-halogen/purescript-halogen/tree/master/docs There's some...

Does this proposal include expanding: > types of kind `* -> *` to: > types of kind `Type -> Type` ?

Found this issue while trying to figure out what other packages use `purescript-gen` besides `purescript-quickcheck`. Seems like this is a task for the registry. Discussed a bit in https://github.com/purescript/registry/issues/27 Maybe...