781111ef35
Each of `{D,Subd}iagnosticMessage::{Str,Eager}` has a comment:
```
// FIXME(davidtwco): can a `Cow<'static, str>` be used here?
```
This commit answers that question in the affirmative. It's not the most
compelling change ever, but it might be worth merging.
This requires changing the `impl<'a> From<&'a str>` impls to `impl
From<&'static str>`, which involves a bunch of knock-on changes that
require/result in call sites being a little more precise about exactly
what kind of string they use to create errors, and not just `&str`. This
will result in fewer unnecessary allocations, though this will not have
any notable perf effects given that these are error paths.
Note that I was lazy within Clippy, using `to_string` in a few places to
preserve the existing string imprecision. I could have used `impl
Into<{D,Subd}iagnosticMessage>` in various places as is done in the
compiler, but that would have required changes to *many* call sites
(mostly changing `&format("...")` to `format!("...")`) which didn't seem
worthwhile.
24 lines
726 B
Rust
24 lines
726 B
Rust
// The compiler code necessary to support the compile_error! extension.
|
|
|
|
use rustc_ast::tokenstream::TokenStream;
|
|
use rustc_expand::base::{self, *};
|
|
use rustc_span::Span;
|
|
|
|
pub fn expand_compile_error<'cx>(
|
|
cx: &'cx mut ExtCtxt<'_>,
|
|
sp: Span,
|
|
tts: TokenStream,
|
|
) -> Box<dyn base::MacResult + 'cx> {
|
|
let Some(var) = get_single_str_from_tts(cx, sp, tts, "compile_error!") else {
|
|
return DummyResult::any(sp);
|
|
};
|
|
|
|
#[expect(
|
|
rustc::diagnostic_outside_of_impl,
|
|
reason = "diagnostic message is specified by user"
|
|
)]
|
|
#[expect(rustc::untranslatable_diagnostic, reason = "diagnostic message is specified by user")]
|
|
cx.span_err(sp, var.to_string());
|
|
|
|
DummyResult::any(sp)
|
|
}
|