github/codegraph
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Mark Swift as completed for receiver type extraction

Browse Source 
Swift methods in extension blocks are already parsed correctly by tree-sitter, which treats `extension Type { }` as `class_declaration` and automatically includes the owner type in qualified names. No getReceiverType implementation needed.
This commit is contained in:
Colby McHenry
2026-04-06 11:49:25 -05:00
parent c0c8a3bb43
commit fba9da53cd
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/SEARCH_QUALITY_LOOP.md
+1 -1
View File
@@ -174,6 +174,7 @@ if (receiverType) {
## Languages Completed ## Languages Completed
- [x] **Go** — `getReceiverType` extracts receiver from `func (sl *Type) method()` - [x] **Go** — `getReceiverType` extracts receiver from `func (sl *Type) method()`
- [x] **Swift** — NOT needed. Tree-sitter parses `extension Type { }` as `class_declaration`, so methods already get owner type in `qualified_name` (e.g., `SimplifyApply.swift::SimplifyApply.swift::ApplyInst::simplify`)
## Languages To Do ## Languages To Do
@@ -181,7 +182,6 @@ Check these — only add `getReceiverType` if methods are top-level (not nested
- [ ] Rust — methods in `impl Type { }` blocks - [ ] Rust — methods in `impl Type { }` blocks
- [ ] C++ — out-of-class method definitions `Type::method()` - [ ] C++ — out-of-class method definitions `Type::method()`
- [ ] Swift — methods in `extension Type { }` blocks
- [ ] Kotlin — extension functions `fun Type.method()` - [ ] Kotlin — extension functions `fun Type.method()`
Verify these DON'T need it (methods nested in class body → qualified name should already be correct): Verify these DON'T need it (methods nested in class body → qualified name should already be correct):