@matklad I started on this yesterday. I've got something that builds and I think all it needs are some tests - I was wondering how you envisioned testing this before I start digging too deep into that?
So this is about the impure "outer" layer of rust analyzer. For these things, I think integration tests work best
We have a couple of em in
Great, I'll look there. I've got something implemented that I think makes sense, but I probably won't think of all the edge cases that there might be straight away.
I don't think we need to think about all edge cases, we can fix them as we go
also cc @Taylor Cramer : this is about make rust-analyzer working without Cargo, I think you might be interested in this as well.
@matklad One problem I'm running into is that I can't specify a absolute path in the
rust-project.json file in my test (as that gets written in a random tmp directory) but the vfs code expects absolute paths (because that's what Cargo normally is providing). Any ideas?
(at least, that's my understanding of why I'm seeing exactly nothing work)
Hm, how tmp sir prevents using an abs path?
Nevermind, managed to fix it.
It will likely need a lot of changes, but it's a start.
@davidtwco that's a compiler bug: rust-analyzer#826
Huh, interesting. Thanks.