As per https://discourse.llvm.org/t/pull-request-migration-schedule/71595 we should move this review to GitHub to make sure we don't lose track of it.
Please use GitHub pull requests for new patches. Phabricator shutdown timeline
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Wed, Sep 6
As per https://discourse.llvm.org/t/pull-request-migration-schedule/71595 we should move this review to GitHub to make sure we don't lose track of it.
Aug 24 2023
LGTM
LGTM
Aug 22 2023
Nice!
LGTM
Aug 21 2023
Did this change not affect ordering of the symbols in the generated JSON? Looks pretty good to me otherwise!
LGTM!
Aug 18 2023
LGTM
LGTM
LGTM
LGTM
Aug 16 2023
Looks mostly good. Quick Question how do we handle inheritance to a template parameter?
Aug 15 2023
LGTM
Aug 9 2023
LGTM
Aug 4 2023
LGTM
Aug 2 2023
LGTM
Jul 31 2023
LGTM!
Looking pretty good, if you can address the last few bits of feedback I am happy to merge this.
Jul 3 2023
LGTM thanks for working on this!
Jun 30 2023
Jun 28 2023
Starting to come together nicely, but I think now would be a good time to write some tests. I am particularly interested in more complex situations like inheritance hierarchies.
May 30 2023
May 26 2023
LGTM with minor changes
May 24 2023
Great start but there are still some rough edges to polish!
May 23 2023
May 4 2023
LGTM
Apr 13 2023
Apr 11 2023
Apr 4 2023
LGTM
Do we still have a test that ensures that actually writing the property attributes manually results in them being added to the declaration fragments?
Mar 30 2023
Mar 29 2023
You will need to rebase this as I made some changes recently to how ExtractAPIVisitor is structured. We can either set up a time to talk about it and do it together or I can handle doing this work once we are happy with this.
Mar 27 2023
Mar 24 2023
In D146656#4220022, @zixuw wrote:LGTM for the ExtractAPIVisitor part.
Remaining:
- update test with @LINE
- the libclang side
Mar 23 2023
Yup looks fine to me!
LGTM, but you should also check in the test that id still renders as expected.
Mar 22 2023
Adding back missing diffs.
Addressing code review feedback
Mar 20 2023
LGTM! I think it's fine to go ahead and land this (premerge check are not a requirement). Have you contributed to LLVM before? If not I will need to commit it on your behalf. Once that is done you should follow the instructions at https://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access to gain commit access if you wish to continue contributing to the project and LLVM in general.
I think there might be some code missing here. Also can you add a test?
Mar 13 2023
LGTM once you fix the test
Mar 2 2023
Feb 28 2023
LGTM, It's worth noting that if the user specifies that an API is unavailable in a later redeclaration, this will be ignored. For example if I add a line to the test void e(void) __attribute__((availability(macos, unavailable))); it will be ignored. Up to you whether you want to fix it now or at a later date.
In D144940#4158143, @Arsenic wrote:In D144940#4158020, @dang wrote:Nice! glad to see this getting fixed. You should add a lit test to ensure we don't regress this behavior in the future.
I see a test checking for availability attribute already exists ( clang/test/ExtractAPI/availability.c ) would it be better if I update it with another function having a platform specific unavailability attribute or should I create a new test file ?
Nice! glad to see this getting fixed. You should add a lit test to ensure we don't regress this behavior in the future.
Feb 10 2023
Jan 24 2023
LGTM for the ExtractAPI changes.
Jan 19 2023
Formatting fixes
Dec 16 2022
Dec 15 2022
Dec 14 2022
Dec 13 2022
Dec 12 2022
Rename new libclang APIs to make the names more readable.
Rebase and fix clang format issue
Dec 9 2022
Address code review feedback regarding libclang specific work.