You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The code path that resolves/typechecks the crate in driver::pretty_print_input is quite a bit out of sync with the equivalent code in driver::compile_input. It doesn't inject core, and it doesn't resolve external crates.
Probably the solution involves factoring most of compile_input into a function that operators on a crate and takes some arguments that allow callers to determine precisely which stages to run on it.
The text was updated successfully, but these errors were encountered:
The code path that resolves/typechecks the crate in
driver::pretty_print_input
is quite a bit out of sync with the equivalent code indriver::compile_input
. It doesn't injectcore
, and it doesn't resolve external crates.Probably the solution involves factoring most of
compile_input
into a function that operators on a crate and takes some arguments that allow callers to determine precisely which stages to run on it.The text was updated successfully, but these errors were encountered: