4 ms·
To counter that I've got a pretty moderate size Rust project that uses hyper, websockets, glium and a bunch of other libraries. RLS + VSCode has been incredible
by vvanders 9y ago
To counter that I've got a pretty moderate size Rust project that uses hyper, websockets, glium and a bunch of other libraries. RLS + VSCode has been incredible solid.
It's come a long way in the last few months, I'd recommend giving it a shot again.
- bpicolo 9y agoThe lack of code-inlined error reporting is still a big miss (unless I'm using the extensions wrong somehow). It's also pretty complicated to get right in rust as the errors tend to link through to multiple files for lifetime issue and such. I started tinkering with a version of this yesterday for vscode. Hoping to get a sane v0 off the ground. Would be cool to have a linter that can run file-by-file as well, though that's tough for clippy as a compiler plugin it seems? Maybe just hacking it to only report on a particular file would work.
- vvanders 9y ago> code-inlined error reporting is still a big miss Do you mean errors next to lines? If so that works today in the RLS variant. You get a red highlight and can mouse-over for details.
- bpicolo 9y agoHmm. I've had trouble getting that working. Will have to toy with it more.
- deleted 9y ago[deleted]
- bpicolo 9y agoFor me this only seems to work in the legacy racer mode (in https://github.com/editor-rs/vscode-rust https://github.com/editor-rs/vscode-rust). Have you had success in RLS mode? RLS just spits stuff into console. =|
- chillee 9y agoI've gotten RLS mode to work for VSCode personally. I've had issues with larger projects, but for smaller projects it seems to work fine.