[cfe-dev] Seeking maintainers of the clang-c interface and the cindex Python wrapper
David Blaikie via cfe-dev
cfe-dev at lists.llvm.org
Mon Dec 2 08:26:33 PST 2019
Richard Smith (as code owner of Clang) is probably the decider here (cc'd)
- and, yeah, it's a bit awkward having an owner who hasn't previously had
commit access etc - but that seems to me to be the nature of finding owners
for abandoned components like this. So I'm leaning towards "yeah, this
seems reasonable" (but might require some of us folks who don't have much
involvement to at least review a few of your patches to check we're
generally on the same page with regards to design, etc).
On Tue, Nov 26, 2019 at 3:47 PM Arthur Peters via cfe-dev <
cfe-dev at lists.llvm.org> wrote:
> Hello all,
> I have a couple of revisions to the clang-c API (the C interface in
> libclang) and to the Python wrapper of it (cindex). But I have not been
> able to find a maintainer who could review these changes.
> Are there current maintainers for these components?
> If there is not, I may be willing to take on at least the Python component
> given that I have found it very useful and expect to continue using it.
> Would this be useful to the community? (I don't yet have commit access or
> anything, so I know it would be a process.)
> PS: The existing revisions which need review are: D70358: Add
> Cursor.get_reference_name_range to clang python binding
> <https://reviews.llvm.org/D70358> https://reviews.llvm.org/D10833 , and D10833:
> Retrieve BinaryOperator::getOpcode and BinaryOperator::getOpcodeStr via
> libclang and its python interface <https://reviews.llvm.org/D10833>
> https://reviews.llvm.org/D70358 (which I commandeered and updated). I
> also have several other changes locally that I would like to push once I
> get a hang for the process. The are all extensions and bug fixes for
> clang-c and cindex.
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev