Different info in docs in AST methods

[4JustMe4]

Here and here we can see similar code samples and same examples:

cxxMemberCallExpr(on(callExpr()))

In the first case, it is written that the object must not be matched:

/// cxxMemberCallExpr(on(callExpr()))
///   does not match `(g()).m()`, because the parens are not ignored.

In the second case, it is written that the object must be matched:

/// cxxMemberCallExpr(on(callExpr()))
///   matches `(g()).m()`.

I think that parens are ignored

[github-actions]

Thank you for submitting a Pull Request (PR) to the LLVM Project!

This PR will be automatically labeled and the relevant teams will be notified.

If you wish to, you can add reviewers by using the "Reviewers" section on this page.

If this is not working for you, it is probably because you do not have write permissions for the repository. In which case you can instead tag reviewers by name in a comment by using @ followed by their GitHub username.

If you have received no comments on your PR for a week, you can request a review by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate is once a week. Please remember that you are asking for valuable time from other developers.

If you have further questions, they may be answered by the LLVM GitHub User Guide.

You can also ask questions in a comment on this PR, on the LLVM Discord or on the forums.

[llvmbot]

@llvm/pr-subscribers-clang

Author: Mikhnenko Sasha (4JustMe4)

Changes

Here and here we can see similar code samples and same examples:

cxxMemberCallExpr(on(callExpr()))

In the first case, it is written that the object must not be matched:

/// cxxMemberCallExpr(on(callExpr()))
///   does not match `(g()).m()`, because the parens are not ignored.

In the second case, it is written that the object must be matched:

/// cxxMemberCallExpr(on(callExpr()))
///   matches `(g()).m()`.

I think that parens are ignored

---

Full diff: https://github.com/llvm/llvm-project/pull/112190.diff

1 Files Affected:

• (modified) clang/include/clang/ASTMatchers/ASTMatchers.h (+1-1)

diff --git a/clang/include/clang/ASTMatchers/ASTMatchers.h b/clang/include/clang/ASTMatchers/ASTMatchers.h
index f1c72efc238784..6c8d900927f2d4 100644
--- a/clang/include/clang/ASTMatchers/ASTMatchers.h
+++ b/clang/include/clang/ASTMatchers/ASTMatchers.h
@@ -4199,7 +4199,7 @@ AST_MATCHER_P_OVERLOAD(QualType, references, internal::Matcher<Decl>,
 ///     cxxRecordDecl(hasName("Y")))))
 ///   matches `y.m()`, `x.m()` and (g()).m(), but not `x.g()`.
 /// cxxMemberCallExpr(on(callExpr()))
-///   does not match `(g()).m()`, because the parens are not ignored.
+///   does match `(g()).m()`, because the parens are ignored.
 ///
 /// FIXME: Overload to allow directly matching types?
 AST_MATCHER_P(CXXMemberCallExpr, onImplicitObjectArgument,

[AaronBallman]

Thank you for this! You should also run clang/docs/tools/dump_ast_matchers.py to regenerate the documentation.

[4JustMe4]

The suggestions have been applied. The document re-generation script has been launched.

[AaronBallman]

LGTM!

[github-actions]

@4JustMe4 Congratulations on having your first Pull Request (PR) merged into the LLVM Project!

Your changes will be combined with recent changes from other authors, then tested by our build bots. If there is a problem with a build, you may receive a report in an email or a comment on this PR.

Please check whether problems have been caused by your change specifically, as the builds can include changes from many authors. It is not uncommon for your change to be included in a build that fails due to someone else's changes, or infrastructure issues.

How to do this, and the rest of the post-merge process, is covered in detail here.

If your change does cause a problem, it may be reverted, or you can revert it yourself. This is a normal part of LLVM development. You can fix your changes and open a new PR to merge them again.

If you don't get any reports, no action is required from you. Your changes are working as expected, well done!