Namespaced prefixes — next step for resolving name clashes

So #92 was somewhat resolved with this PR #120

The next step is to eventually publish a version of fantasy-land npm package with namespaced prefixed names.

There are some questions to discuss though:

• When do we release the new version? Should we wait until majority of libs migrate to the new approach, or should we release it right away so two versions will coexist allowing everyone to choose on which versions to depend in each particular case?
• How the prefixed names should look like?

Maybe there more questions, these two is what came to my mind.

[rpominov]

I think this is the best way to do it, create normal methods in your API like with “old” FL, and then do something like:

Type.prototype[FL.map] = Type.prototype.map
Type.prototype[FL.ap] = Type.prototype.ap
...

We could even provide a helper that does this automatically:

import {makeFantasyLandCompatible} from 'fantasy-land/compat-helper'

makeFantasyLandCompatible(Type)

[Avaq]

I wonder if there is a way to have both without sacrificing anything? – @SimonRichardson

In Fluture I did this thing where I create keys for both 'map' and FL.map on my type, so when FL adds namespaces, my API won’t change, and FL dispatchers will still work.