rniwa wrote:
> I'm also somewhat terrified of returning C++ objects from ObjC methods by
> value, ever since I learned that when you call an ObjC method on a nil it
> returns a _zero-initialized_ object without calling a constructor on it.
Yikes. I didn't know that!
https://github.com/llvm/ll
https://github.com/rniwa closed https://github.com/llvm/llvm-project/pull/108669
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
haoNoQ wrote:
I'm also somewhat terrified of returning C++ objects from ObjC methods by
value, ever since I learned that when you call an ObjC method on a nil it
returns a _zero-initialized_ object without calling a constructor on it.
https://github.com/llvm/llvm-project/pull/108669
__
https://github.com/haoNoQ approved this pull request.
Yeah sounds about right!
The property syntax is confusing, I don't have enough expertise to confirm that
`getResultExpr()` is the right solution so I think we should keep trying and
incrementally figuring out what's going on.
Setters proba
https://github.com/rniwa updated
https://github.com/llvm/llvm-project/pull/108669
>From 241fde13679b85e63126318520cd3f19029f49ad Mon Sep 17 00:00:00 2001
From: Ryosuke Niwa
Date: Fri, 13 Sep 2024 19:01:57 -0700
Subject: [PATCH 1/2] [alpha.webkit.UncountedCallArgsChecker] Add support for
Object
llvmbot wrote:
@llvm/pr-subscribers-clang-static-analyzer-1
Author: Ryosuke Niwa (rniwa)
Changes
Treat a function call or property access via a Objective-C++ selector which
returns a Ref/RefPtr as safe.
---
Full diff: https://github.com/llvm/llvm-project/pull/108669.diff
4 Files Affect
https://github.com/rniwa created
https://github.com/llvm/llvm-project/pull/108669
Treat a function call or property access via a Objective-C++ selector which
returns a Ref/RefPtr as safe.
>From 241fde13679b85e63126318520cd3f19029f49ad Mon Sep 17 00:00:00 2001
From: Ryosuke Niwa
Date: Fri, 13