4 ms·
Xcode's new autocomplete is pretty awful. It tries to be smart, but keeps hallucinating nonexistent API methods, and makes up stuff from my own codebase.
by ChrisMarshallNY 2y ago
Xcode's new autocomplete is pretty awful. It tries to be smart, but keeps hallucinating nonexistent API methods, and makes up stuff from my own codebase.
- 3836293648 2y agoIs it actually making stuff up or is it falsely believing that some type conforms to a protocol it doesn't?
- jshier 2y agoIt fully makes things up, like nonexistent parameters to real functions. In the areas where it's accurate it's barely better than the existing autocomplete, though I have noticed it seems to deal a bit better with broken code (which also breaks Swift's compiler-based tooling). It can also generate larger things like type definitions a bit better, but Apple never really invested into autocomplete, so it's not really anything better than what other IDEs already had.
- ChrisMarshallNY 2y agoOh yeah. For example: I may have a method in my class: straightenCheese(byDegrees: CGFloat) The "helpful" autofill might give me: straightenCheese(by: Double) If I'm lucky, but it's more likely to give: strengthenCheese(by: Double)
- KETHERCORTEX 2y agoHow can anyone come to the conclusion that it's a good idea to use imprecise generation on the go in the tool made to refer to specific already defined things? Year 2024. Now we use more computing power to make computers remember things worse.