Re:LSP-AI: open-source language server serving as back end f...
by verdverm on Saturday June 08, 2024 @12:26PM
(#40618630)
For 4, this is where I think using the target language(s) LSP / intellesense would be useful. The AI tools should know that I'm referring to a specific tables/types/libraries through references/locality/imports and supply that automatically to the context for me.
[ Parent
| on HN ]
Re:LSP-AI: open-source language server serving as back end f...
by simonw on Saturday June 08, 2024 @12:31PM
(#40618671)
Copilot does that in a really clever way already: any time it performs a completion it looks at other nearby files in the project and tries to find pieces of code that look semantically similar to the area you are editing, then includes those snippets in its prompt.
This works well as a general rule, but sometimes it doesn't fine the right snippets - which is why I occasionally help it out through copy and paste.
Re:LSP-AI: open-source language server serving as back end f...
by verdverm on Saturday June 08, 2024 @12:54PM
(#40618836)
As described, that seems to miss out on files that are far away through imports, and if not similar to existing code, such as when writing unique code.
My main thoughts behind this are that
1. The LLMs tend to hallucinate library functions
2. I don't want to have to copy and paste a schema