purescript-deprecated / purescript-base Goto Github PK

I'm putting together a PR to fix #2, and wondered whether you'd be open to trimming the dependencies a little. Things like free, transformers and distributive are certainly useful, but I don't think they are in line with the stated goal of the package (to "ease the development of PureScript applications by bundling mutually compatible versions of common functional libraries into a single package"). Are these libraries really "common"?

I'd suggest it would be more useful to package up things which would turn this into a "batteries-included Prelude" for those who want such a thing.

I'll send a PR soon anyway to see what you think.

With module reexports, maybe it makes sense to have a Base module here which reexports things like Data.Maybe, Data.Either, etc.

Then import Base would give you a pretty useable system.

We'd have to be careful not to export too much, since we can't selectively reexport right now.

Could you please make a new release so that v1.0.0...master could come into effect?

We intend to deprecate this library as part of a purescript-contrib cleanup -- see the full discussion on Discourse for more details on the effort.

We're considering deprecating purescript-base because it hasn't seen activity in years (including several compiler versions) and because in the age of package sets (see Spago) this library is no longer needed.

"Deprecation" means that this library either moves to a private maintainer or is moved to the purescript-deprecated organization and made read-only. If the library is deprecated it can still be installed but it won't receive future updates.

Please feel free to weigh in on this discussion either here or in the Discourse discussion.

To make this usable, we need a script that bumps versions to the most recent set of mutually compatible versions, builds the packages, and runs all their tests.

Seems like something in the bower ecosystem could be leveraged to do this.

Doing this will alleviate a number of unfortunate explicit resolutions in various packages.

@jdegoes Is this yours?