LSP doesn't provide completion for interfaces Lisette version: 0.2.11 IDE: VSCode and…
- User
LSP doesn't provide completion for interfaces Lisette version: 0.2.11 IDE: VSCode and Zed
The LSP isn't providing completions for interfaces from either stdlib or user-defined.
interface Example { fn example(self, name: string) -> string } fn example_call(ex: Example) -> string { ex. }Interface
No new interfaces are introduced.
- Assistant
I’ll trace completion member resolution for concrete types versus interfaces, add a focused regression test for both user-defined and stdlib interfaces, then run the relevant test suite.
- Assistant
The failure is localized: interface methods are stored on the interface definition with the
selfreceiver removed, while completion only scans ordinary method definitions and requires the first parameter to be the receiver type. I’m checking interface inheritance and visibility semantics before patching so embedded/parent methods behave consistently too. - Assistant
The first regression test is in place and compilation is underway. The implementation now reads methods directly from interface definitions and recursively includes embedded parent-interface methods, with cycle and duplicate protection.
- Assistant
Both regressions now pass, including
go:io.Reader. I’m running the complete LSP integration suite next to catch interactions with struct, enum, chained, and cross-module completion paths.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- fable-5Compare side by side →
- fable-5Compare side by side →