Yeah I think @cuviper is right in that we'll only want to have a whitelist for rustc dependencies right now, which currently have the most impact. New dependencies in libstd, for example, can cause quite a lot of ripples and new dependencies in rustc even can sometimes cause problems.
So that would mean I should BFS the dependency DAGs of crates beginning with âlibrustc.â and 'libsyntax.â, right? Are there any other crates I should look at?
Ah you can probably start at the rustc crate which represents the executable itself, and I think nowadays youâd also want to start at rustc_trans, but that should do the trick!
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.