-
Notifications
You must be signed in to change notification settings - Fork 62
RLS is not linting properly #310
Comments
I think the reason is the same as for #307 |
@KalitaAlexey that is what I thought too, but unlike those issues, my RLS doesn't crash. In that first "message" JSON I can see where it is throwing the error, but maybe VSCODE isn't translating correctly? |
@dhicksNTIA, |
@KalitaAlexey here are the outputs of "Rust Language Server":
|
I'm working on #289. |
@KalitaAlexey If you want, I can take a stab at it. I am not familiar with the source, but is there a place I should start? |
@DirtGrubDylan I would be glad if you helped.
You can analyze it yourself.
My output is:
I hope that's clear enough. |
@KalitaAlexey So after playing around with the debugger this morning. I found that my bug is not with the linter. It is with the watcher. Using your
but, if I add an empty
to
then the linter quits working, and I get:
|
It appears that having both a I have tried just having a |
@nrc, |
It looks like having 2 main functions could be causing the issue. I had |
@watzon, |
I had this issue when opening a folder above multiple rust folders (thus having multiple main functions). It was fixed when I did what @watzon suggested. |
Version of VSCode: 1.13.1
Version of the extension: 0.4.2
OS: Linux Mint 18
Description:

RLS is not linting like it used to. Consider the following image:
Before, RLS would red underline that bad return value, now it does nothing. Was this change intentional?
Output of the "Rust logging" channel:
Output of the "Rust logging" channel:
The text was updated successfully, but these errors were encountered: