Florian Diebold
Florian Diebold
> The rustc's coerce_unsized solving is ten years old(https://github.com/rust-lang/rust/pull/24619/files#diff-12aa26d34290be9b45ffddf48028dd5af1991fbc8a069414b3ecc250cf48dd0aR295) and I think that this is not so much dependent on sophisticated trait solving infra; it mostly does things by itself...
No, `select` isn't the same as full trait solving.
3G on a codebase that includes Iced is not excessive, it's pretty much within expectations.
Or a GitHub discussion.
Yeah, and it's really annoying that we can't easily reproduce these in the Chalk test harness... Might this be rust-lang/chalk#688 again?
Hmm, this doesn't reproduce for me.
One could imagine a scheme where rust-analyzer checks for a running server and forks and daemonizes if one isn't running yet, maybe shutting itself down automatically if there aren't any...
I'd note that the file format for case 3 doesn't need to be the same as our internal cache format for cases 1 and 2 -- we could have e.g....
> should rust-analyzer use the cache as is (mmap it basiccally), or should it parse it into salsa's internal data structures? I think it'd be super interesting to use rkyv...
It means the way to resolve this issue is to fix it in Chalk. (The first step towards that would be writing a Chalk test to reproduce it, and making...