[haskell-llvm] support for multiple LLVM versions in llvm-base

Nathan Howell nathan.d.howell at gmail.com
Sat May 18 20:27:00 BST 2013


On Sat, May 18, 2013 at 11:00 AM, Henning Thielemann <
lemming at henning-thielemann.de> wrote:

> Since the 'llvm' package also must provide a fixed API depending only on
> its version, it will be hard to provide a constant API for different
> versions of llvm-base (using ifdef).
>

LLVM does add and remove functions from version to version, so there is no
reason to assume stabillity of the base layer. So you're saying that we
need to have tightly coupled releases of the FFI and all the other
packages, which I'm also in agreement with.

>  'mtl' is a new dependency that was not needed for llvm-base before. And
also: 'transformers' would be nicer, since it is simpler.

I think mtl is a fine dependency, even if it's not new. The high level
bindings, include your llvm-tf package depend on it already. If you'd like
to port it to transformers we'll consider patches via pull requests.

 Apart from that, the project structure currently becomes broken. We have
> three levels of interfaces in one repository, where the low and mid level
> are merged in one package. They reside in the 'base' directory and are
> affected by the configure procedure. In contrast to that, the high-level
> interface has no such directory.


I don't find it useful to split the FFI bindings out to a separate package.
I also find tightly coupled packages that live in multiple repositories to
be difficult to work with. Since this is a matter of taste, I doubt we'll
come to any further agreement in this thread. If you'd like to continue the
discussion please file a ticket: https://github.com/bos/llvm/issues.

thanks,
-n
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://projects.haskell.org/pipermail/haskell-llvm/attachments/20130518/3b333d49/attachment.htm>


More information about the Haskell-llvm mailing list