-
Notifications
You must be signed in to change notification settings - Fork 13.5k
nicer autodiff error handling #142842
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
base: master
Are you sure you want to change the base?
nicer autodiff error handling #142842
Conversation
Some changes occurred in compiler/rustc_codegen_ssa |
Please give the commit a proper commit message 😆 |
acde7fc
to
f21fac3
Compare
cc @Sa4dUs that should prevent your issue in the future. |
f21fac3
to
5c4b6cc
Compare
ok, I'm happy with these two tests, let me know if you want any changes. |
5c4b6cc
to
3610d7c
Compare
@@ -419,7 +419,12 @@ fn generate_lto_work<B: ExtraBackendMethods>( | |||
} else { | |||
if !autodiff.is_empty() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe pick a random (like the first) entry from this list and use its span so in case of a larger crate the user is aware of why this is being emitted. I could see it being confusing in case someone is adding cfgs to turn on/off autodiff and got sth wrong in the process
I still intend to finish #137570 by adding proper handling for library builds.
I was hoping to directly get the proper fix in, but I haven't had the time in a while, and other contributors and early testers run into this issue often enough.