Florian Diebold

Results 137 comments of Florian Diebold

The modeling of closures in Chalk's test framework is somewhat different from ours, and often it's not possible to reproduce issues with them, in particular if variables are involved. So...

What's the second bug?

The problem doesn't reproduce for me. I'm not sure the choice of target folder is actually the problem, considering the file _does_ exist :thinking: I assume restarting VSCode does not...

I don't really see how rust-analyzer could cause an ICE in rustc that can't be otherwise triggered. We're only running `cargo` as normal subprocesses. So this should still be reported...

> As a side note this can't be the real problem regarding None as it is the only item from std::prelude that causes problems. It's just one of the more...

We don't have a way of prompting the user when there are ambiguous imports, but apart from that I think we should have this. (We could even try to be...

It's not parser recovery; it's this: https://github.com/rust-lang/rust-analyzer/blob/5982d9c420d0dc90739171829f0d2e9c80d98979/crates/hir-expand/src/fixup.rs#L151-L161 (Original code by me, FIXME added by @Veykril and he's of course correct ;) )

Btw, I've been thinking a possible UI for this (within the constraints of LSP) could be a 'move item here' assist on `use` items... so you have something like ```rust...

(and another possibility in that 'toolbox' would then be an `inline import` assist to get rid of the reexport...)