AI loves context and types are providing context to AI that it can search in other files to see how a certain type is implemented or how to call a function. Now, with loon all the type information is hidden, so context is hidden behind the compiler and the editor. Even when I'm reading code through Github, without the LSP, I have no idea what the types are. I trust the compiler that the code works, but I'm missing context to write new code, which is what AI does.
So maybe there should be a header file like OCaml that prints the type information for each function in its implementation file or a very fast CLI tool call should exist that AI can use to get the type of a function. As long as our LLMs work on text data, the type information should be printed out somewhere.
But again, maybe I'm wrong and this structure is great for AI. I'm seeing Claude commits to the repo, so I'm curious how the experience has been so far.
AI loves context and types are providing context to AI that it can search in other files to see how a certain type is implemented or how to call a function. Now, with
loonall the type information is hidden, socontextis hidden behind the compiler and the editor. Even when I'm reading code through Github, without the LSP, I have no idea what the types are. I trust the compiler that the code works, but I'm missing context to write new code, which is what AI does.So maybe there should be a header file like OCaml that prints the type information for each function in its implementation file or a very fast CLI tool call should exist that AI can use to get the type of a function. As long as our LLMs work on text data, the type information should be
printed outsomewhere.But again, maybe I'm wrong and this structure is great for AI. I'm seeing Claude commits to the repo, so I'm curious how the experience has been so far.