v-analyzer
v-analyzer copied to clipboard
Bring IDE features for V programming languages in VS Code, Vim and other editors
### Describe the bug When creating an inline function and instantly calling it, the type does not correctly get inferred: ```V // Inferred type for t is `unknown` t :=...
### Describe the bug There is no type inferrence for the `os.join_path` function. For example: ``` tmp := os.join_path(root, 'tmp') ``` `tmp` will be inferred as `unknown` and the `os.join_path`...
### Describe the bug v-analyzer should not remove un-used imports. These are compiler warnings, sure, but if the imports are removed toggling code (commenting, and then un-commentating) will create compiler...
### Describe the bug Items/tokens are not recognized correctly inside type cast operator in both neovim and vscode ### Expected Behavior Correct items/tokens inside type cast ### Current Behavior -...
### Describe the bug `:Inspect` command shows wrong item name for function call on imported namespace `:Inspect` command shows wrong item name for module being imported ### Expected Behavior function...
### Describe the feature How would this be configured in Lazyvim? ### Use Case Using Lazyvim ### Other Information _No response_
### Describe the bug V-analyzer reports error when file with module is in root directory on same level as file containing `main` function ### Expected Behavior No error ### Current...
### Describe the bug the extension spins up a new instance of v on each save that never exits, the result is that the extension stops working / crashes every...
### Describe the bug ```v module test import cli {Command} fn main() { mut cmd := Command{...} } ```  Variable `cmd` will be marked as `:unknown` and logs says:...
### Describe the bug In the nightly-version this information pops up.  Here's the complete output: ```text [Info - 9:53:21 PM] v-analyzer version: 0.0.2-beta.1, OS: linux x64 [Info - 9:53:21...