-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose more packages #11
Comments
I would suggest adding:
|
at which point we could just as well expose a bunch more from their collective transitive dependency set: aeson assoc async attoparsec attoparsec base16 base64 base-compat base-compat-batteries base-orphans bifunctors comonad contravariant data-array-byte data-fix distributive dlist effectful effectful-core generically hashable indexed-traversable indexed-traversable-instances integer-logarithms monad-control OneTuple primitive QuickCheck random safe-exceptions scientific semialign semigroupoids splitmix StateVar strict tagged text-short th-abstraction these time-compat transformers-base transformers-compat unliftio unliftio-core unordered-containers uuid-types vector vector-stream witherable |
It looks like a solid set of packages indeed! |
It would also be important to list in a "about" page/modal the list of these packages and their version as their appear in the freeze file |
https://play-haskell.tomsmeding.com/saved/4PHAIH1d bunch of packages available now, these to be precise |
Basic functionality has been implemented, remaining work is in #17 |
Currently we expose only the GHC boot libs, which excludes potentially useful stuff like
random
. There is a design question here: how much do we want to expose? All of hackage is nigh impossible, all of stackage is potentially possible but very resource-hungry and frankly overkill. Installing packages on-demand is a rathole I'd rather not get into, I think. What to do?The text was updated successfully, but these errors were encountered: