Include bindings in the LLVM project

[zimmski]

The bindings are almost complete. There are some parts that have to be manually written (like the function pointers) and some parameters need to be handled differently to make the API complete (e.g. go-clang/gen#23) but besides from that, there is nothing really lacking.

So I was wondering if we should start the process of getting included into the main LLVM project? Is that even possible, and does it make sense?

[sbinet]

I suppose it is possible (Andrew Wilkins (@axw) did that for go-llvm)
There are a few issues with migrating the bindings to upstream:

• the CLang git-repo is quite big (196M), so cloning it takes a while (I believe go-1.6 will shallow-clone the 5 latest revisions, but still)
• the import path will be longer (and it seems the meta-import for llvm.org/llvm.v37/bindings/go/llvm doesn't work)

That said, I am not against it but we have to carefully consider this move.

[zimmski]

OK that does not sound good. I would like to keep the bindings as small as possible. I do not think that cloning a ~200mb repository is user-friendly at all.

Maybe we could just push for being "mentioned" in the documentation and release announcements? "Looking for Go bindings to clang-c?"

[sbinet]

SGTM.

[zimmski]

Should this happen with the official announcements on the Go mailing lists, or is this an independent announcement?