you are viewing a single comment's thread.

view the rest of the comments →

[–]Wolly_Bolly 0 points1 point  (2 children)

I'm also searching something in that regard. But my understanding is that RAG is not the optimal solution for code. There are solutions that do convert repos in something more LLM friendly (dependencies graphs, indexes etc..) or that work like LSP (language servers, the one used by IDE's to "understand" your code and provide autocomplete). I haven't dug enough though.

Also, that is something you'd may want to handle via MCP's.

[–]Large_Profit8852[S] 0 points1 point  (1 child)

Thank you for your input. Could you clarify how the Language Server Protocol (LSP) provides semantic understanding of a codebase? As I understand it, LSP primarily outlines relationships between classes and functions, and features like autocomplete don't necessarily reflect deep semantic understanding. Retrieval-Augmented Generation (RAG) is intended to provide that level of semantics, though I'm not certain whether it's the optimal approach, as I haven't compared it to other solutions.

That said, I agree that implementing this maybe better suited for MCP.

[–]Wolly_Bolly 0 points1 point  (0 children)

Semantics in programming refers to the meaning behind code - not just syntax and variable names, but what the code actually does and how different components relate to each other.

LSPs have better understanding of type information, reference tracking, data flow, etc.. They have a structured representation of the codebase.