Future of clang-pure

[Merivuokko]

Hello @chpatrick, do you have any plans for maintaining clang-pure in the future? Like fixing bugs, incorporating new features from libclang, accepting PRs, or anything?

I might have use for this package, and might consider forking it, if it turns out to that it is able to do what I want. I probably would need to extend clang-pure somewhat. I also have no idea about how many new features have been added to libclang, if any.

I might also consider upstreaming my changes. However, there are things that I am not that much interested in – like maintaining backwards-compatibility with older ecosystem packages or support for the Stack tool.

[chpatrick]

Hi there!

Unfortunately I don't have much time to maintain it these days and you're very welcome to do so if you like. I can also add you as a contributor to this repo.

I've had some ideas about a new version of the package, mainly doing the reference counting with C++ smart pointers instead of Foreign.Concurrent:

https://github.com/chpatrick/clang-pure-2/blob/master/cbits/ClangPure.h

[Merivuokko]

Unfortunately I don't have much time to maintain it these days and you're very welcome to do so if you like. I can also add you as a contributor to this repo. This sounds like a good possibility. However, I prefer to gain more experience both with clang and clang-pure before writing to the repo. This of course does not mean that you couldn't add me as a contributor already, but patches won't appear right away. I forked clang-pure and have been working on a private branch. I have so far added new query functions for Cursors and Types. I'm planning to introduce a lot of breakage though by changing source code and identifier representation from ByteString to Text, as Clang is guaranteed to return only UTF-8. I've had some ideas about a new version of the package, mainly doing the reference counting with C++ smart pointers instead of Foreign.Concurrent: https://github.com/chpatrick/clang-pure-2/blob/master/cbits/ClangPure.h I'll take a look at this to see how complex this would be to implement.

[chpatrick]

You can see how I do the reference counting stuff here: https://github.com/chpatrick/clang-pure-2/blob/master/src/Language/C/Clang/Internal/FFI.hs#L41

…

On Mon, Oct 9, 2023 at 3:06 PM Merivuokko ***@***.***> wrote: > Unfortunately I don't have much time to maintain it these days and you're > very welcome to do so if you like. I can also add you as a contributor to > this repo. This sounds like a good possibility. However, I prefer to gain more experience both with clang and clang-pure before writing to the repo. This of course does not mean that you couldn't add me as a contributor already, but patches won't appear right away. I forked clang-pure and have been working on a private branch. I have so far added new query functions for Cursors and Types. I'm planning to introduce a lot of breakage though by changing source code and identifier representation from ByteString to Text, as Clang is guaranteed to return only UTF-8. > I've had some ideas about a new version of the package, mainly doing the reference counting with C++ smart pointers instead of Foreign.Concurrent: > https://github.com/chpatrick/clang-pure-2/blob/master/cbits/ClangPure.h I'll take a look at this to see how complex this would be to implement. — Reply to this email directly, view it on GitHub <#26 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGLJTY2DREMBX6LGXL4FI3X6PZF7AVCNFSM6AAAAAA5TASMN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJSHE3TQNJXGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>