-
Notifications
You must be signed in to change notification settings - Fork 23
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
Huge dependencies due to Void #5
Comments
I really don't know what to think about this one. To split off this |
:( (I wouldn't want you to go through that trouble, I'd rather maintain a private fork for Android development purposes then.) If it were controlled by an optional flag that we could disable, would that be too much hassle? Or too ugly, for that matter? It would mean adding the flag to the cabal file (flag def + (compiler option -DVOID + build-depends) controlled by that flag), and changing the haskell file (CPP pragma, plus imports and instance enclosed in #ifdef). |
Thanks for the flag suggestion. I'm open to that possibility, but I'd like to explore some alternatives. The |
void is now in base: https://hackage.haskell.org/package/base-4.8.1.0/docs/Data-Void.html |
@sboosali Oh, wow. I'm delighted to hear that |
let me know if this builds https://github.com/sboosali/MemoTrie/commit/28c647163b98b66592e32dae29afcd107b60defd note:
however, this is my first time dealing with different compiler versions. I spent the past half hour reading through: https://hackage.haskell.org/package/lens-4.13/src/lens.cabal and and that's all I know. someone else might also want to take a look at this too. |
(and, your package is amazing! it blew my mind when I saw how sums became products and products became functions) |
@sboosali Thanks for investigating! Your branch does indeed compile fine for me in GHC 7.8.2. I attached a question in your commit. |
The Void instance of HasTrie has the following transitive dependencies:
I'm wondering whether that instance shouldn't belong elsewhere. Does it add real value?
Context: We'd like to make Yampa depend on vector-space, but bringing along so many deps to save us 15 lines of code seems like an overkill. Yampa is being used to develop Android games, so size is pretty important.
The text was updated successfully, but these errors were encountered: