Rebuild rust-analyzer when launching in VS Code

[jonas-schievink]

This is usually the right thing, and previously would launch a stale r-a server.

[matklad]

Shouldn’t we run both tasks on build?

[jonas-schievink]

Probably, yeah. I'd have to make an extra task then, since you can only specify one in the launch configuration.

[jonas-schievink]

It seems that you can't make a launch configuration depend on a background task (it will wait indefinitely for the task to finish)

[jonas-schievink]

Okay this seems to work, but I have no clue about npm or TypeScript

[matklad]

bors r+

I feel like this can be in theory trimmed down a bit, as it seems like we shouldn't have that many different compbinations. but I also don't have any specific suggestions here, as I don't use tasks at all :)

[bors]

Build succeeded:

• Rust (macos-latest)
• Rust (ubuntu-latest)
• Rust (windows-latest)
• TypeScript

[felix91gr]

I'm sorry to bother you guys, but what does this do exactly? Are you rebuilding r-a?

But r-a is (more or less) a compiler.
Wouldn't rebuilding it take way too long? Therefore, I'm assuming I got it wrong and it's something else that's being rebuilt.
Unless it's being rebuilt incrementally?

[flodiebold]

@felix91gr As far as I know, these are tasks for use while developing rust-analyzer in VSCode. And yeah, an incremental build of rust-analyzer doesn't take that long.