-
Notifications
You must be signed in to change notification settings - Fork 1
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
Feature/dependency pruning #27
Conversation
131728f
to
24eddcb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The project does not build as is. The test suite depends on aeson
as well.
Ok, the test suite actually should depend on |
ah yep. I need to add that to my workflow. |
6b1b217
to
a0d2a10
Compare
OK So this now checks out. Lotta work to maintain the json stuff. Does it actually buy us anything or can we move to make the test vectors into in-haskell values? |
a0d2a10
to
62ab499
Compare
This PR should be squashed on merge. |
62ab499
to
7a3ad4b
Compare
7a3ad4b
to
b62d19a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there some way to simplify the process of parsing test vectors out of JSON encoded sources? Ideally the JSON code would be totally minimal and purpose built to deal with the test vectors. So we would not need e.g. NetBox
and JsonBox
.
Probably. However, this change was primarily concerned with removing aeson and mtl from the main library code. I didn't really audit whether the code itself was "optimal". Personally I don't like the fact that we are giving typeclass instances to Keep in mind that a future PR will be moving from |
All right. I don't mind going back for a cleanup pass. The instances don't bother me much since they are confined to the test suite. |
Actually I can revamp this code during the hedgehog patch. |
Closes #17 and #19