4 ms·
It 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, tho
by jshier 2y ago
It 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)