A modern programming language that makes developers happier.

kotlinlang

Hey Guys,
I was working on docs for `Apply`, but
I am not sure of the practicality of `Apply` in `Arrow`, most functions etc, we use are build on top of `Applicative` or `Functor`. I could not find anything theoretically substantial to promote using `Functor` over `Apply` in some general use cases. Data types like `Map` have valid `Apply` instances, but no `Applicative`. Most of the typeclass machinery in Arrow is build on top of either `Functor` or `Applicative`.

My question is: Can we delete Apply, because it may have instances for any DT that has an `Applicative`, but there is nothing we can do with an `Apply`, because the `Functor` has more to offer.

If we choose to keep it, for Articles and a like. I will keep my branch with the changes and push a PR in the next couple of days

I see the point of `Apply` now and move forward with my PR.

Apply on map is a good use case since map frequently shows up in generic encoders and decoders for serialization