Removing Hoopl dependency?
Herbert Valerio Riedel
hvriedel at gmail.com
Sat May 27 18:28:09 UTC 2017
On 2017-05-27 at 19:58:11 +0200, Michal Terepeta wrote:
> I've done an experiment in  (to see how much we'd need to actually
> copy) and I really like the result:
> - We can remove one external dependency and git submodule at the
> cost of only 5 new modules in `cmm/Hoopl` (net gain of only 4
> modules: we add 5 new but can remove `cmm/Hoopl`, which is no longer
> - We should be able to fix all of the above issues and make the code
> easier to understand (less code, everything in one repo, fewer
> - It's going to be easier to change things since we don't need to
> worry about changing the public interface of Hoopl (it's a
> standalone package on Hackage and other people already depend on the
> current behavior).
> What do you think? Does anyone think we shouldn't do this?
It appears to me that in this case, the benefits in gained flexibility
outweight the cost of independent development and potential loss of
synergies. So I'm +1 on this.
More information about the ghc-devs