-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
onboarding friction log #88
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Logging friction I encountered trying to onboard...
run
andrun_with_tcx
would be nice.use rustc_smir::{run, rustc_internal}
.ControlFlow
-- what doesContinue
vsBreak
mean in this context? What type arguments should I give? (I think Continue means "no error" and Break lets me pass back an error value? unclear.)object
only shows up once)feature(rustc_private)
? On the crate? What if this is a library dependency of another crate?It'd be really nice to have a simpler entry point, maybe even on crates.io, that automatically compiled to some fallback when nightly is not available.
The text was updated successfully, but these errors were encountered: