Skip to content

Commit 7bd9cbc

Browse files
committed
docs(bench): mention constructor FN alongside receiver-typed FNs in objc threshold comment
The previous comment only listed receiver-typed instance message sends as unresolved false negatives, omitting the constructor edge (run → UserService.initWithRepository:). Both modes are FNs; the comment now lists them together so future contributors see the complete picture.
1 parent 29dd101 commit 7bd9cbc

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

tests/benchmarks/resolution/resolution-benchmark.test.ts

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -188,8 +188,9 @@ const THRESHOLDS: Record<string, { precision: number; recall: number }> = {
188188
// New fixture languages — no parser or call resolution yet
189189
// objc: class-method static calls and same-class calls resolve at 100% precision, 46% recall.
190190
// Expected-edges now use full ObjC selectors (createUserWithId:name:email:, isValidEmail:, etc.)
191-
// matching what the ObjC extractor emits. Receiver-typed instance message sends
192-
// are not yet resolved — tracked as FNs. Precision 1.0 acts as ratchet against future FPs.
191+
// matching what the ObjC extractor emits. Constructor message sends (initWithRepository:) and
192+
// receiver-typed instance message sends are not yet resolved — tracked as FNs.
193+
// Precision 1.0 acts as ratchet against future FPs.
193194
objc: { precision: 1.0, recall: 0.4 },
194195
cuda: { precision: 0.0, recall: 0.0 },
195196
groovy: { precision: 0.0, recall: 0.0 },

0 commit comments

Comments
 (0)