You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use Nix and I'm playing around with agda2hs, but it's been hard to do all the wiring necessary for this to work. I do not know how much work would that entail, but I am happy to help with that.
The text was updated successfully, but these errors were encountered:
This would be great! There's a few things we can improve with the current nix setup, perhaps it would make sense to do a sprint and file within one PR? My wishlist would be:
As you say, having agda2hs-lib available in agdaPackages. I think this one would be the least amount of work - just about adding a derivation here and here.
We have a custom agda2hs derivation that is almost a copy of the upstream agda derivation. Would love to drop that.
We ship agda2hs-executable without agda2hs-lib linked since then one can add other libraries on top (--library-file flags that the derivation uses don't stack, afaik). It would be much nicer to have both agda2hs with the library and have the ability to add new libraries. Perhaps something like this can be done by always adding agda2hs-lib to withPackages list?
It would be good to have a builder that takes agda2hs library and produces an haskell derivation.
Devise some sensible naming scheme for all the derivations we expose in lib and packages now.
The first one is least intrusive against nixpkgs, the others will probably require some patches, e.g. so that we can re-use upstream agda derivation.
I use Nix and I'm playing around with
agda2hs
, but it's been hard to do all the wiring necessary for this to work. I do not know how much work would that entail, but I am happy to help with that.The text was updated successfully, but these errors were encountered: