Stream: t-compiler/rust-analyzer

Topic: Improvement for runnables


Mr Smeet (Feb 16 2020 at 15:08, on Zulip):

Now I am trying to provide closer integration of runnable's detection with cargo. Who dug the project more deeply? Is there any way to get information about project layout? And also i am interested about module futures.
Sorry if this is a noobish

matklad (Feb 16 2020 at 15:47, on Zulip):

What exactly do you have in mind for "close integration"? It might be a good idea to take a look at https://github.com/rust-analyzer/rust-analyzer/pull/3153, which touches many relevant thigns

Mr Smeet (Feb 16 2020 at 16:46, on Zulip):

So, when we analyze runnable we should respect project layout. For example main func entry point maybe located only in path that defined in manifest or default path also main not always entry point
https://doc.rust-lang.org/cargo/reference/manifest.html
https://doc.rust-lang.org/cargo/reference/manifest.html#configuring-a-target

In addition, we can not extract runnable if we have multiple definition or another kind of problem with locally correction of code

Mr Smeet (Jul 25 2020 at 13:05, on Zulip):

(deleted)

Mr Smeet (Aug 06 2020 at 04:52, on Zulip):

How i can get FileId by string path?

Laurențiu (Aug 06 2020 at 05:12, on Zulip):

vfs.file_id, I think, if you have access to it

Mr Smeet (Aug 07 2020 at 04:51, on Zulip):

I will try to reformulate the question. How i can resolve std::process::Termination for getting it implementation in std library

Last update: Jul 28 2021 at 04:45UTC