rustc: have run_compiler bubble up compilation results #8009
Conversation
|
why? |
|
run_compiler is the simplest interface to rustc as a library, but actually using it is impossible unless you just want its side-effects. not using it means you need to build the configuration and parse arguments yourself (for the case where you want to have the same arguments as rustc). I need this for rustdoc_ng; if there's another simple way to accomplish this, I must have missed it. |
|
oh. I didn't land the patch here I meant to. improves the interface substantially. lemme dig it up, 1 sec. |
|
sorry I'm late getting back to this: #8077 is the branch I had in mind. If you like it (and I suggest possibly running it by a couple other core devs), land it and close this one. It's how I'd prefer to handle the clunkiness of |
|
If #8077 was satisfactory, can we close this? |
|
Yep. |
…t, r=giraffate Allow `suboptimal_flops` in const functions This PR allows `clippy::suboptimal_flops` in constant functions. The check also effects the `clippy::imprecise_flops` lint logic. However, this doesn't have any effects as all functions checked for are not const and can therefore not be found in such functions. --- changelog: [`suboptimal_flops`]: No longer triggers in constant functions Closes: rust-lang/rust-clippy#8004
No description provided.