[llvm-bugs] [Bug 50309] New: -Wunguarded-availability warns on lambdas and nested classes that are correctly guarded

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=50309

            Bug ID: 50309
           Summary: -Wunguarded-availability warns on lambdas and nested
                    classes that are correctly guarded
           Product: clang
           Version: trunk
          Hardware: Macintosh
                OS: MacOS X
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: Frontend
          Assignee: unassignedclangbugs at nondot.org
          Reporter: logan.r.smith0 at gmail.com
                CC: llvm-bugs at lists.llvm.org, neeilans at live.com,
                    richard-llvm at metafoo.co.uk

The bodies of lambdas and nested class member functions aren't correctly
analyzed by -Wunguarded-availability even when they occur entirely inside an
appropriate @available check. Blocks work as expected.

The following code produces warnings on the marked lines, and suggests wrapping
the inner function calls in @available checks, even though they are already
inside one in the outer context:

// clang -cc1 -xobjective-c++ -triple x86_64-apple-macosx10.9
-Wunguarded-availability -fblocks -fsyntax-only
int func_10_12() __attribute__((availability(macos, introduced = 10.12)));

void foo() {
    if (@available(macos 10.12, *)) {
        (void)[] { func_10_12(); }; // warning here
        struct X { void f() { func_10_12(); } }; // warning here

        (void)^{ func_10_12(); }; // no warning here, as expected
    }
}

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20210512/4fcd437c/attachment-0001.html>