Roberto Vidal

They update from time to time, but this one has been skipped :shrug: https://github.com/gitpod-io/workspace-images/pull/554

Unfortunately, it is half-expected. I think `rls` (and similar tools, like `rust-analyzer`) expect a [conventional project structure](https://doc.rust-lang.org/cargo/guide/project-layout.html), imposed by `cargo`, to be able to effectively analyze your code. `rustlings` on...

I fear that toying with symlinks and manipulating the file system will introduce more complexity that we can chew. I'm not sure how mature rust-analyzer, for instance, is with regards...

> Can you expand more on this? It was mostly a random thought inspired by the aforementioned Jetbrains packaging of Rustlings. I think creating those highly-integrated experiences in your editor...

That sounds pretty cool, though I'd be a bit reluctant to merge anything if we as maintainers cannot test it :sweat_smile:

@rouilleux Would you be able to try again, but installing `rustlings` from [this branch](https://github.com/jrvidal/rustlings/tree/rustc-exists)? Also, what OS are you using?

That's strange... We perform a dry run of the same procedure that rustlings will use to run your exercises, `Command::new(...).spawn()`, which is the standard way to launch a command... :thinking:...

My guess this is the same as #443: the rustlings project structure is _not_ that of a standard Rust project and IDEs choke with it. Not idea why it used...

FYI I've deployed half a fix for this. We now highlight some lifetime generic parameters e.g. https://jrvidal.github.io/explaine.rs/?code=struct+Foo%3C%27a%3E+%7B%0A++x%3A+%26%27a+i32%0A%7D&line=0&ch=12

Phew, that sounds a bit daunting at this point :sweat_smile: Good suggestion though.