Model the query dependency graph #19042
Labels
A-documentation
docs for rust-analyzer usage/inner working
A-salsa
might be a salsa issue
Broken Window
Bugs / technical debt to be addressed immediately
(to be done after the salsa migration)
No one really has a clear picture on our queries, their individual purposes, their dependencies, etc. Given we are going to touch all of this with the salsa migration over time we might as well try to document all of this properly (and maybe generate a fancy visual dependency graph while we are at it).
What's the use in this? The dependencies we draw between queries are fairly important wrt to incrementality, which I believe has severely worsened the past 2 years, causing us to become fairly slow for (supposedly) trivial edits in documents! (one reason for this is the span map, it is not incremental friendly... we likely need to add an extra firewall query for that).
And on the topic of the word firewall query, a glossary might be nice as well :)
The text was updated successfully, but these errors were encountered: