Avoid polluting globals about functional-programming-jargon HOT 2 OPEN

While I agree, we'd have to either create our own List or some other type that implements all the relevant type classes. I have mixed feelings on whether that'd make it harder to understand

• if we choose to create List is the reader gonna ask "Why are you reimplementing array in a feature-poor way?"
• If we choose Maybe then it may be trying to teach too many ideas at once.
• If we choose Identity then it becomes hard to justify as valuable and stay terse.

from functional-programming-jargon.

Maybe defining everything in terms of static-land instead of fantasy-land would be better. https://github.com/fantasyland/static-land

from functional-programming-jargon.