Skip to content
TheChatArchiveThe Chat Archive
gpt-5.6-sol· openaiHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

LSP doesn't provide completion for interfaces Lisette version: 0.2.11 IDE: VSCode and…

  1. 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.

  2. 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.

  3. Assistant

    The failure is localized: interface methods are stored on the interface definition with the self receiver 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.

  4. 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.

  5. 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.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.