-
Notifications
You must be signed in to change notification settings - Fork 8
Add a flag for avoiding various boot libs #29
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
base: master
Are you sure you want to change the base?
Conversation
|
Is this discussed with maintainers of |
|
Well, sjakobi had expressed a potential interest in having strict-containers be part of containers, and one stepping stone to that would be to have |
|
I really want to be sure about that GHC is fine of I'm in support of pushing that all that code into "bundled with GHC" basket, but there have to be a broad agreement and clear plan. Concretely: boot flag is no-go if |
|
Yes, there is further work to be done if it were actually a boot library. My point was that having this PR included in a release on Hackage, makes it easier to explore the possibilities because then public PRs don't need to point to private copies of The discussion is a little bit premature at the moment because I didn't explore the issue concretely yet, but I imagine turning Map, HashMap, etc into typeclasses containing basic constructors/destructors as methods, so that separate lazy vs strict types can implement those, similar to how Vector.Generic works already. Not sure if @sjakobi had any other thoughts. But I meant to take this slowly, didn't want to rush anyone into a discussion yet. |
|
I'm not accepting experimental features in proper releases, Make a sdist from a branch, upload it somewhere, use |
I'm experimenting with de-duplicating StrictPair/StrictMaybe out of the containers library and need this flag to break the dependency cycle strict -> binary -> containers -> strict.