summaryrefslogtreecommitdiffstats
path: root/clang/tools/c-index-test/c-index-test.c
diff options
context:
space:
mode:
authorJordan Rose <jordan_rose@apple.com>2013-04-26 21:43:01 +0000
committerJordan Rose <jordan_rose@apple.com>2013-04-26 21:43:01 +0000
commit9de821ebfd344b04b45df335dc324d3d126ef42a (patch)
tree7e52e3e2f6ee72256507f0f457b327068e2c3493 /clang/tools/c-index-test/c-index-test.c
parent9661c1d18a1c494031eb9fa116e4a965c20c8af5 (diff)
downloadbcm5719-llvm-9de821ebfd344b04b45df335dc324d3d126ef42a.tar.gz
bcm5719-llvm-9de821ebfd344b04b45df335dc324d3d126ef42a.zip
[analyzer] An ObjC for-in loop runs 0 times if the collection is nil.
In an Objective-C for-in loop "for (id element in collection) {}", the loop will run 0 times if the collection is nil. This is because the for-in loop is implemented using a protocol method that returns 0 when there are no elements to iterate, and messages to nil will result in a 0 return value. At some point we may want to actually model this message send, but for now we may as well get the nil case correct, and avoid the false positives that would come with this case. <rdar://problem/13744632> llvm-svn: 180639
Diffstat (limited to 'clang/tools/c-index-test/c-index-test.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud