Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Export `String` in CorePrelude instead of BasicPrelude #33

Closed
nikita-volkov opened this Issue Jan 5, 2013 · 2 comments

Comments

Projects
None yet
3 participants
Contributor

nikita-volkov commented Jan 5, 2013

I'm not sure what the reasoning was behind the choice to export it in BasicPrelude, but because of this the ClassyPrelude lacks this essential type. Alternatively consider this a request to export String in ClassyPrelude.

Owner

snoyberg commented Jan 5, 2013

The theory (which is definitely debatable) was that String usage should be discouraged very strongly in classy-prelude. I tend to agree with you that this was a bad call though, and have no problem moving the export from BasicPrelude to CorePrelude.

Collaborator

DanBurton commented Jan 5, 2013

I concur. Whether or not we wish to discourage the use of String, it is so important to so many libraries and the traditional Haskell programmer mentality in general, I agree that the String export should be moved to CorePrelude.

@snoyberg snoyberg closed this in 4e3cf2e Mar 4, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment