Closed CodaFi closed 9 years ago
Fine with me. Full higher kinds are needed for any sort of true type class or Swiftish protocol
to accurately represent monads, so any kind of kludge is acceptable right now.
In response to discussion on typelift/Aquifer#10, we should consider using >>->>
for (forward) Kleisli composition.
Fixed by the merge of #249.
I've been playing around with generalizing the Monad operators so we don't have to write them all out for a couple months and have come to the conclusion it's just too inelegant even if it were possible. In the spirit of choosing the lesser of two evils, and not furthering bloat in
Monad
, I think the best course of action is to factor out the operators and functions into some kind ofMonadOps
protocol and implement them all.It's a one-time yak shaving, but a yak shaving all the same.
Related to #136