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
Neither of which seems particularly good. The former is last updated in 2017; the latter is only 1500 lines of Haskell, but all undocumented, it implements some crazy reference counting, for reasons unclear, and doesn't have many of the features we need.
The goal here is not to we write our own general purpose bindings, but instead implement some sane bindings for our own use. Unlike what clang-pure does, I think we should not provide any kind of cursors, or try to share memory with libclang, but instead traverse the AST using the libclang interface, construct a pure Haskell value it, managed on the Haskell heap, and then be done with libclang from that point on.
The text was updated successfully, but these errors were encountered:
There are two existing bindings on hackage:
Neither of which seems particularly good. The former is last updated in 2017; the latter is only 1500 lines of Haskell, but all undocumented, it implements some crazy reference counting, for reasons unclear, and doesn't have many of the features we need.
The goal here is not to we write our own general purpose bindings, but instead implement some sane bindings for our own use. Unlike what
clang-pure
does, I think we should not provide any kind of cursors, or try to share memory withlibclang
, but instead traverse the AST using thelibclang
interface, construct a pure Haskell value it, managed on the Haskell heap, and then be done withlibclang
from that point on.The text was updated successfully, but these errors were encountered: