\On Sat, May 29, 2021 at 10:57 PM Raphael Isemann <teempe...@gmail.com> wrote:
> And I think the best way to propose a new API is maybe just making a > dummy patch that adds the API + documentation (doesn't need an actual > implementation or tests). And if everyone agrees the new API is fine > you can add the tests and implementation. By making a patch you also > automatically get everyone subscribed to your patch via Herald rules > or people reading the mailing list. > > If you don't want to make patches, I think bug reports on > bugs.llvm.org could also work. Most of the thing you describe sound > like they don't need a lot of effort to implement/test, so there's a > good chance someone will implement it for you. > I've just created https://reviews.llvm.org/D103375 for one of the pieces. I used to have commit access, but the last time I used it was before the move to GitHub, so I don't mind doing the work and landing things myself ... I don't want to create much of a burden on others! Thanks for your feedback! - Bruce
_______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
