Kleisli: flatMapF and andThen are the same

[ceedubs]

Currently Kleisli has two methods flatMapF and andThen that have duplicated type signatures and implementations.

This andThen is an overloaded version that takes a function as opposed to a Kleisli.

I propose keeping flatMapF and removing the andThen that uses Function1 to prevent confusion and avoid overloading. What do people think?

[julienrf]

Do you also want to remove compose overloads?

I must say that I quite like the name “andThen”, but I understand your argument (especially the one about overloading).

BTW, I’d like to have a symbolic alias “>=>” for “andThen”, I can’t see one in syntax, am I missing something?

[ceedubs]

@julienrf all good questions. I'm not sure I have good answers :). I do agree about liking the name andThen. I generally avoid overloading, but I think that maybe some other Cats folks (like maybe @non?) are more open to it.

As far as I know >=> doesn't currently exist. Were you thinking of making this generic syntax for anything in ComposeOps? I'm pretty neutral on that, so whatever other people think.

[travisbrown]

+1 from me for removing the overloaded andThen and compose (if only for the inconvenience caused by the overloads breaking eta-expansion).