-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No in-editor warnings when using indexing on a bad type #134
Comments
The |
I also faced similar problem warnings / errors aren't shown in VSCode. It worked only after enabling
|
Build on save seems o have fixed this but it also seems like a slightly sub-par experience. Having to save and wait for a build to do some type checking like that really slows down development iterations. Is there a reason it has to be build on save or it has to be built at all to get this kind of error showing in the editor? |
After enabling |
@akhildevelops are you on linux or Mac? I'm on windows (something I probabaly should've mentioned earlier.) |
On Linux, why would that matter ? |
I just know sometimes tooling is worse on windows that other OS's which I've had experience before and could be something windows specific that means this setting isn't working for my setup. Just trying to narrow down possible causes. |
Based on my experimentation, it's possible that you have My English is not very good, the above is translated by Deelp. |
I'm trying to learn Zig and using VSCode for it, I'm using an array list and while I've figured out I need to use
arrList.items[0]
I'm still curious why i'm not getting the error in-editor before i compile it, this seems like a normal part of tooling and it is really making it difficult to learn the language.Am I missing something here or is this not something that is implemented?
Thanks in advance.
The text was updated successfully, but these errors were encountered: