2019-10-09 01:23:10 +00:00
|
|
|
//! Contains `ParseSess` which holds state living beyond what one `Parser` might.
|
|
|
|
//! It also serves as an input to the parser itself.
|
|
|
|
|
2021-09-29 00:39:30 +00:00
|
|
|
use crate::config::CheckCfg;
|
2022-09-30 01:38:15 +00:00
|
|
|
use crate::errors::{FeatureDiagnosticForIssue, FeatureDiagnosticHelp, FeatureGateError};
|
2022-08-17 11:52:47 +00:00
|
|
|
use crate::lint::{
|
|
|
|
builtin::UNSTABLE_SYNTAX_PRE_EXPANSION, BufferedEarlyLint, BuiltinLintDiagnostics, Lint, LintId,
|
|
|
|
};
|
2020-02-29 17:37:32 +00:00
|
|
|
use rustc_ast::node_id::NodeId;
|
2022-09-01 14:22:30 +00:00
|
|
|
use rustc_data_structures::fx::{FxHashMap, FxHashSet, FxIndexSet};
|
2023-03-14 12:11:56 +00:00
|
|
|
use rustc_data_structures::sync::{AppendOnlyVec, AtomicBool, Lock, Lrc};
|
2020-01-02 10:41:57 +00:00
|
|
|
use rustc_errors::{emitter::SilentEmitter, ColorConfig, Handler};
|
2022-03-24 02:03:04 +00:00
|
|
|
use rustc_errors::{
|
2022-09-30 01:38:15 +00:00
|
|
|
fallback_fluent_bundle, Diagnostic, DiagnosticBuilder, DiagnosticId, DiagnosticMessage,
|
2022-09-01 10:40:43 +00:00
|
|
|
EmissionGuarantee, ErrorGuaranteed, IntoDiagnostic, MultiSpan, Noted, StashKey,
|
2022-03-24 02:03:04 +00:00
|
|
|
};
|
2020-01-02 10:41:57 +00:00
|
|
|
use rustc_feature::{find_feature_issue, GateIssue, UnstableFeatures};
|
2019-12-31 17:15:40 +00:00
|
|
|
use rustc_span::edition::Edition;
|
|
|
|
use rustc_span::hygiene::ExpnId;
|
|
|
|
use rustc_span::source_map::{FilePathMapping, SourceMap};
|
2022-03-24 02:03:04 +00:00
|
|
|
use rustc_span::{Span, Symbol};
|
2019-10-09 01:23:10 +00:00
|
|
|
|
2022-09-02 08:29:40 +00:00
|
|
|
use rustc_ast::attr::AttrIdGenerator;
|
2019-10-09 01:23:10 +00:00
|
|
|
use std::str;
|
|
|
|
|
2019-11-29 21:09:00 +00:00
|
|
|
/// The set of keys (and, optionally, values) that define the compilation
|
|
|
|
/// environment of the crate, used to drive conditional compilation.
|
2022-09-01 14:22:30 +00:00
|
|
|
pub type CrateConfig = FxIndexSet<(Symbol, Option<Symbol>)>;
|
2021-09-29 00:39:30 +00:00
|
|
|
pub type CrateCheckConfig = CheckCfg<Symbol>;
|
2019-11-29 20:45:26 +00:00
|
|
|
|
2019-10-09 01:23:10 +00:00
|
|
|
/// Collected spans during parsing for places where a certain feature was
|
|
|
|
/// used and should be feature gated accordingly in `check_crate`.
|
|
|
|
#[derive(Default)]
|
2019-10-30 16:34:00 +00:00
|
|
|
pub struct GatedSpans {
|
|
|
|
pub spans: Lock<FxHashMap<Symbol, Vec<Span>>>,
|
2019-10-30 15:38:16 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
impl GatedSpans {
|
|
|
|
/// Feature gate the given `span` under the given `feature`
|
|
|
|
/// which is same `Symbol` used in `active.rs`.
|
|
|
|
pub fn gate(&self, feature: Symbol, span: Span) {
|
|
|
|
self.spans.borrow_mut().entry(feature).or_default().push(span);
|
|
|
|
}
|
|
|
|
|
|
|
|
/// Ungate the last span under the given `feature`.
|
|
|
|
/// Panics if the given `span` wasn't the last one.
|
|
|
|
///
|
|
|
|
/// Using this is discouraged unless you have a really good reason to.
|
|
|
|
pub fn ungate_last(&self, feature: Symbol, span: Span) {
|
|
|
|
let removed_span = self.spans.borrow_mut().entry(feature).or_default().pop().unwrap();
|
|
|
|
debug_assert_eq!(span, removed_span);
|
|
|
|
}
|
|
|
|
|
|
|
|
/// Is the provided `feature` gate ungated currently?
|
|
|
|
///
|
|
|
|
/// Using this is discouraged unless you have a really good reason to.
|
|
|
|
pub fn is_ungated(&self, feature: Symbol) -> bool {
|
|
|
|
self.spans.borrow().get(&feature).map_or(true, |spans| spans.is_empty())
|
|
|
|
}
|
2019-10-30 16:34:00 +00:00
|
|
|
|
|
|
|
/// Prepend the given set of `spans` onto the set in `self`.
|
|
|
|
pub fn merge(&self, mut spans: FxHashMap<Symbol, Vec<Span>>) {
|
|
|
|
let mut inner = self.spans.borrow_mut();
|
|
|
|
for (gate, mut gate_spans) in inner.drain() {
|
|
|
|
spans.entry(gate).or_default().append(&mut gate_spans);
|
|
|
|
}
|
|
|
|
*inner = spans;
|
|
|
|
}
|
2019-10-09 01:23:10 +00:00
|
|
|
}
|
|
|
|
|
2020-04-25 01:38:31 +00:00
|
|
|
#[derive(Default)]
|
|
|
|
pub struct SymbolGallery {
|
2020-08-02 15:20:00 +00:00
|
|
|
/// All symbols occurred and their first occurrence span.
|
2020-08-05 07:29:13 +00:00
|
|
|
pub symbols: Lock<FxHashMap<Symbol, Span>>,
|
2020-04-25 01:38:31 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
impl SymbolGallery {
|
|
|
|
/// Insert a symbol and its span into symbol gallery.
|
2022-03-16 12:12:30 +00:00
|
|
|
/// If the symbol has occurred before, ignore the new occurrence.
|
2020-04-25 01:38:31 +00:00
|
|
|
pub fn insert(&self, symbol: Symbol, span: Span) {
|
|
|
|
self.symbols.lock().entry(symbol).or_insert(span);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2020-01-02 10:55:00 +00:00
|
|
|
/// Construct a diagnostic for a language feature error due to the given `span`.
|
|
|
|
/// The `feature`'s `Symbol` is the one you used in `active.rs` and `rustc_span::symbols`.
|
2023-04-09 21:07:18 +00:00
|
|
|
pub fn feature_err(
|
|
|
|
sess: &ParseSess,
|
2020-01-02 10:41:57 +00:00
|
|
|
feature: Symbol,
|
|
|
|
span: impl Into<MultiSpan>,
|
2023-02-04 01:59:17 +00:00
|
|
|
explain: impl Into<DiagnosticMessage>,
|
2023-04-09 21:07:18 +00:00
|
|
|
) -> DiagnosticBuilder<'_, ErrorGuaranteed> {
|
2020-01-02 10:41:57 +00:00
|
|
|
feature_err_issue(sess, feature, span, GateIssue::Language, explain)
|
|
|
|
}
|
|
|
|
|
2020-01-02 10:55:00 +00:00
|
|
|
/// Construct a diagnostic for a feature gate error.
|
|
|
|
///
|
|
|
|
/// This variant allows you to control whether it is a library or language feature.
|
|
|
|
/// Almost always, you want to use this for a language feature. If so, prefer `feature_err`.
|
2022-10-31 15:14:29 +00:00
|
|
|
#[track_caller]
|
2023-04-09 21:07:18 +00:00
|
|
|
pub fn feature_err_issue(
|
|
|
|
sess: &ParseSess,
|
2020-01-02 10:41:57 +00:00
|
|
|
feature: Symbol,
|
|
|
|
span: impl Into<MultiSpan>,
|
|
|
|
issue: GateIssue,
|
2023-02-04 01:59:17 +00:00
|
|
|
explain: impl Into<DiagnosticMessage>,
|
2023-04-09 21:07:18 +00:00
|
|
|
) -> DiagnosticBuilder<'_, ErrorGuaranteed> {
|
2022-08-17 11:52:47 +00:00
|
|
|
let span = span.into();
|
|
|
|
|
|
|
|
// Cancel an earlier warning for this same error, if it exists.
|
|
|
|
if let Some(span) = span.primary_span() {
|
2023-04-09 21:07:18 +00:00
|
|
|
if let Some(err) = sess.span_diagnostic.steal_diagnostic(span, StashKey::EarlySyntaxWarning)
|
|
|
|
{
|
|
|
|
err.cancel()
|
|
|
|
}
|
2022-08-17 11:52:47 +00:00
|
|
|
}
|
|
|
|
|
2023-02-04 01:59:17 +00:00
|
|
|
let mut err = sess.create_err(FeatureGateError { span, explain: explain.into() });
|
2022-02-28 20:29:06 +00:00
|
|
|
add_feature_diagnostics_for_issue(&mut err, sess, feature, issue);
|
|
|
|
err
|
|
|
|
}
|
|
|
|
|
2022-08-17 11:52:47 +00:00
|
|
|
/// Construct a future incompatibility diagnostic for a feature gate.
|
|
|
|
///
|
|
|
|
/// This diagnostic is only a warning and *does not cause compilation to fail*.
|
2022-12-20 21:10:40 +00:00
|
|
|
pub fn feature_warn(sess: &ParseSess, feature: Symbol, span: Span, explain: &str) {
|
2022-08-17 11:52:47 +00:00
|
|
|
feature_warn_issue(sess, feature, span, GateIssue::Language, explain);
|
|
|
|
}
|
|
|
|
|
|
|
|
/// Construct a future incompatibility diagnostic for a feature gate.
|
|
|
|
///
|
|
|
|
/// This diagnostic is only a warning and *does not cause compilation to fail*.
|
|
|
|
///
|
|
|
|
/// This variant allows you to control whether it is a library or language feature.
|
|
|
|
/// Almost always, you want to use this for a language feature. If so, prefer `feature_warn`.
|
2022-08-22 06:28:50 +00:00
|
|
|
#[allow(rustc::diagnostic_outside_of_impl)]
|
|
|
|
#[allow(rustc::untranslatable_diagnostic)]
|
2022-12-20 21:10:40 +00:00
|
|
|
pub fn feature_warn_issue(
|
|
|
|
sess: &ParseSess,
|
2022-08-17 11:52:47 +00:00
|
|
|
feature: Symbol,
|
|
|
|
span: Span,
|
|
|
|
issue: GateIssue,
|
|
|
|
explain: &str,
|
|
|
|
) {
|
|
|
|
let mut err = sess.span_diagnostic.struct_span_warn(span, explain);
|
|
|
|
add_feature_diagnostics_for_issue(&mut err, sess, feature, issue);
|
|
|
|
|
|
|
|
// Decorate this as a future-incompatibility lint as in rustc_middle::lint::struct_lint_level
|
|
|
|
let lint = UNSTABLE_SYNTAX_PRE_EXPANSION;
|
|
|
|
let future_incompatible = lint.future_incompatible.as_ref().unwrap();
|
|
|
|
err.code(DiagnosticId::Lint {
|
|
|
|
name: lint.name_lower(),
|
|
|
|
has_future_breakage: false,
|
|
|
|
is_force_warn: false,
|
|
|
|
});
|
|
|
|
err.warn(lint.desc);
|
|
|
|
err.note(format!("for more information, see {}", future_incompatible.reference));
|
|
|
|
|
|
|
|
// A later feature_err call can steal and cancel this warning.
|
|
|
|
err.stash(span, StashKey::EarlySyntaxWarning);
|
|
|
|
}
|
|
|
|
|
2022-02-28 20:29:06 +00:00
|
|
|
/// Adds the diagnostics for a feature to an existing error.
|
2022-12-20 21:10:40 +00:00
|
|
|
pub fn add_feature_diagnostics(err: &mut Diagnostic, sess: &ParseSess, feature: Symbol) {
|
2022-02-28 20:29:06 +00:00
|
|
|
add_feature_diagnostics_for_issue(err, sess, feature, GateIssue::Language);
|
|
|
|
}
|
2020-01-02 10:41:57 +00:00
|
|
|
|
2022-02-28 20:29:06 +00:00
|
|
|
/// Adds the diagnostics for a feature to an existing error.
|
|
|
|
///
|
|
|
|
/// This variant allows you to control whether it is a library or language feature.
|
|
|
|
/// Almost always, you want to use this for a language feature. If so, prefer
|
|
|
|
/// `add_feature_diagnostics`.
|
2022-12-20 21:10:40 +00:00
|
|
|
pub fn add_feature_diagnostics_for_issue(
|
2022-02-28 20:29:06 +00:00
|
|
|
err: &mut Diagnostic,
|
2022-12-20 21:10:40 +00:00
|
|
|
sess: &ParseSess,
|
2022-02-28 20:29:06 +00:00
|
|
|
feature: Symbol,
|
|
|
|
issue: GateIssue,
|
|
|
|
) {
|
2020-01-02 10:41:57 +00:00
|
|
|
if let Some(n) = find_feature_issue(feature, issue) {
|
2022-08-22 06:28:50 +00:00
|
|
|
err.subdiagnostic(FeatureDiagnosticForIssue { n });
|
2020-01-02 10:41:57 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// #23973: do not suggest `#![feature(...)]` if we are in beta/stable
|
|
|
|
if sess.unstable_features.is_nightly_build() {
|
2022-08-22 06:28:50 +00:00
|
|
|
err.subdiagnostic(FeatureDiagnosticHelp { feature });
|
2020-01-02 10:41:57 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2019-10-09 01:23:10 +00:00
|
|
|
/// Info about a parsing session.
|
|
|
|
pub struct ParseSess {
|
|
|
|
pub span_diagnostic: Handler,
|
2019-10-15 20:48:13 +00:00
|
|
|
pub unstable_features: UnstableFeatures,
|
2019-10-09 01:23:10 +00:00
|
|
|
pub config: CrateConfig,
|
2021-09-29 00:39:30 +00:00
|
|
|
pub check_config: CrateCheckConfig,
|
2019-10-09 01:23:10 +00:00
|
|
|
pub edition: Edition,
|
2021-08-29 08:34:23 +00:00
|
|
|
/// Places where raw identifiers were used. This is used to avoid complaining about idents
|
|
|
|
/// clashing with keywords in new editions.
|
2023-03-14 12:16:19 +00:00
|
|
|
pub raw_identifier_spans: AppendOnlyVec<Span>,
|
2021-08-29 08:34:23 +00:00
|
|
|
/// Places where identifiers that contain invalid Unicode codepoints but that look like they
|
2021-09-10 07:30:58 +00:00
|
|
|
/// should be. Useful to avoid bad tokenization when encountering emoji. We group them to
|
2021-08-29 08:34:23 +00:00
|
|
|
/// provide a single error per unique incorrect identifier.
|
|
|
|
pub bad_unicode_identifiers: Lock<FxHashMap<Symbol, Vec<Span>>>,
|
2019-10-09 01:23:10 +00:00
|
|
|
source_map: Lrc<SourceMap>,
|
|
|
|
pub buffered_lints: Lock<Vec<BufferedEarlyLint>>,
|
|
|
|
/// Contains the spans of block expressions that could have been incomplete based on the
|
|
|
|
/// operation token that followed it, but that the parser cannot identify without further
|
|
|
|
/// analysis.
|
|
|
|
pub ambiguous_block_expr_parse: Lock<FxHashMap<Span, Span>>,
|
2019-10-30 16:34:00 +00:00
|
|
|
pub gated_spans: GatedSpans,
|
2020-04-25 01:38:31 +00:00
|
|
|
pub symbol_gallery: SymbolGallery,
|
2019-10-29 00:44:20 +00:00
|
|
|
/// The parser has reached `Eof` due to an unclosed brace. Used to silence unnecessary errors.
|
2023-03-14 11:46:48 +00:00
|
|
|
pub reached_eof: AtomicBool,
|
2020-05-03 17:47:51 +00:00
|
|
|
/// Environment variables accessed during the build and their values when they exist.
|
|
|
|
pub env_depinfo: Lock<FxHashSet<(Symbol, Option<Symbol>)>>,
|
2021-04-09 14:35:40 +00:00
|
|
|
/// File paths accessed during the build.
|
|
|
|
pub file_depinfo: Lock<FxHashSet<Symbol>>,
|
2021-01-28 08:24:55 +00:00
|
|
|
/// Whether cfg(version) should treat the current release as incomplete
|
|
|
|
pub assume_incomplete_release: bool,
|
Implement span quoting for proc-macros
This PR implements span quoting, allowing proc-macros to produce spans
pointing *into their own crate*. This is used by the unstable
`proc_macro::quote!` macro, allowing us to get error messages like this:
```
error[E0412]: cannot find type `MissingType` in this scope
--> $DIR/auxiliary/span-from-proc-macro.rs:37:20
|
LL | pub fn error_from_attribute(_args: TokenStream, _input: TokenStream) -> TokenStream {
| ----------------------------------------------------------------------------------- in this expansion of procedural macro `#[error_from_attribute]`
...
LL | field: MissingType
| ^^^^^^^^^^^ not found in this scope
|
::: $DIR/span-from-proc-macro.rs:8:1
|
LL | #[error_from_attribute]
| ----------------------- in this macro invocation
```
Here, `MissingType` occurs inside the implementation of the proc-macro
`#[error_from_attribute]`. Previosuly, this would always result in a
span pointing at `#[error_from_attribute]`
This will make many proc-macro-related error message much more useful -
when a proc-macro generates code containing an error, users will get an
error message pointing directly at that code (within the macro
definition), instead of always getting a span pointing at the macro
invocation site.
This is implemented as follows:
* When a proc-macro crate is being *compiled*, it causes the `quote!`
macro to get run. This saves all of the sapns in the input to `quote!`
into the metadata of *the proc-macro-crate* (which we are currently
compiling). The `quote!` macro then expands to a call to
`proc_macro::Span::recover_proc_macro_span(id)`, where `id` is an
opaque identifier for the span in the crate metadata.
* When the same proc-macro crate is *run* (e.g. it is loaded from disk
and invoked by some consumer crate), the call to
`proc_macro::Span::recover_proc_macro_span` causes us to load the span
from the proc-macro crate's metadata. The proc-macro then produces a
`TokenStream` containing a `Span` pointing into the proc-macro crate
itself.
The recursive nature of 'quote!' can be difficult to understand at
first. The file `src/test/ui/proc-macro/quote-debug.stdout` shows
the output of the `quote!` macro, which should make this eaier to
understand.
This PR also supports custom quoting spans in custom quote macros (e.g.
the `quote` crate). All span quoting goes through the
`proc_macro::quote_span` method, which can be called by a custom quote
macro to perform span quoting. An example of this usage is provided in
`src/test/ui/proc-macro/auxiliary/custom-quote.rs`
Custom quoting currently has a few limitations:
In order to quote a span, we need to generate a call to
`proc_macro::Span::recover_proc_macro_span`. However, proc-macros
support renaming the `proc_macro` crate, so we can't simply hardcode
this path. Previously, the `quote_span` method used the path
`crate::Span` - however, this only works when it is called by the
builtin `quote!` macro in the same crate. To support being called from
arbitrary crates, we need access to the name of the `proc_macro` crate
to generate a path. This PR adds an additional argument to `quote_span`
to specify the name of the `proc_macro` crate. Howver, this feels kind
of hacky, and we may want to change this before stabilizing anything
quote-related.
Additionally, using `quote_span` currently requires enabling the
`proc_macro_internals` feature. The builtin `quote!` macro
has an `#[allow_internal_unstable]` attribute, but this won't work for
custom quote implementations. This will likely require some additional
tricks to apply `allow_internal_unstable` to the span of
`proc_macro::Span::recover_proc_macro_span`.
2020-08-02 23:52:16 +00:00
|
|
|
/// Spans passed to `proc_macro::quote_span`. Each span has a numerical
|
|
|
|
/// identifier represented by its position in the vector.
|
2023-03-14 12:11:56 +00:00
|
|
|
pub proc_macro_quoted_spans: AppendOnlyVec<Span>,
|
2022-09-02 08:29:40 +00:00
|
|
|
/// Used to generate new `AttrId`s. Every `AttrId` is unique.
|
|
|
|
pub attr_id_generator: AttrIdGenerator,
|
2019-10-09 01:23:10 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
impl ParseSess {
|
2021-03-16 05:50:34 +00:00
|
|
|
/// Used for testing.
|
2022-10-17 13:11:26 +00:00
|
|
|
pub fn new(locale_resources: Vec<&'static str>, file_path_mapping: FilePathMapping) -> Self {
|
2022-10-13 09:13:02 +00:00
|
|
|
let fallback_bundle = fallback_fluent_bundle(locale_resources, false);
|
2020-02-22 14:07:05 +00:00
|
|
|
let sm = Lrc::new(SourceMap::new(file_path_mapping));
|
2022-03-26 07:27:43 +00:00
|
|
|
let handler = Handler::with_tty_emitter(
|
|
|
|
ColorConfig::Auto,
|
|
|
|
true,
|
|
|
|
None,
|
|
|
|
Some(sm.clone()),
|
2022-03-28 08:36:20 +00:00
|
|
|
None,
|
2022-03-26 07:27:43 +00:00
|
|
|
fallback_bundle,
|
|
|
|
);
|
2020-02-22 14:07:05 +00:00
|
|
|
ParseSess::with_span_handler(handler, sm)
|
2019-10-09 01:23:10 +00:00
|
|
|
}
|
|
|
|
|
2019-10-10 08:26:10 +00:00
|
|
|
pub fn with_span_handler(handler: Handler, source_map: Lrc<SourceMap>) -> Self {
|
2019-10-09 01:23:10 +00:00
|
|
|
Self {
|
|
|
|
span_diagnostic: handler,
|
2020-10-10 18:27:52 +00:00
|
|
|
unstable_features: UnstableFeatures::from_environment(None),
|
2022-09-01 14:22:30 +00:00
|
|
|
config: FxIndexSet::default(),
|
2021-09-29 00:39:30 +00:00
|
|
|
check_config: CrateCheckConfig::default(),
|
2019-10-09 01:23:10 +00:00
|
|
|
edition: ExpnId::root().expn_data().edition,
|
2023-03-14 12:16:19 +00:00
|
|
|
raw_identifier_spans: Default::default(),
|
2021-08-29 08:34:23 +00:00
|
|
|
bad_unicode_identifiers: Lock::new(Default::default()),
|
2019-10-09 01:23:10 +00:00
|
|
|
source_map,
|
|
|
|
buffered_lints: Lock::new(vec![]),
|
|
|
|
ambiguous_block_expr_parse: Lock::new(FxHashMap::default()),
|
|
|
|
gated_spans: GatedSpans::default(),
|
2020-04-25 01:38:31 +00:00
|
|
|
symbol_gallery: SymbolGallery::default(),
|
2023-03-14 11:46:48 +00:00
|
|
|
reached_eof: AtomicBool::new(false),
|
2020-05-03 17:47:51 +00:00
|
|
|
env_depinfo: Default::default(),
|
2021-04-09 14:35:40 +00:00
|
|
|
file_depinfo: Default::default(),
|
2021-01-28 08:24:55 +00:00
|
|
|
assume_incomplete_release: false,
|
Implement span quoting for proc-macros
This PR implements span quoting, allowing proc-macros to produce spans
pointing *into their own crate*. This is used by the unstable
`proc_macro::quote!` macro, allowing us to get error messages like this:
```
error[E0412]: cannot find type `MissingType` in this scope
--> $DIR/auxiliary/span-from-proc-macro.rs:37:20
|
LL | pub fn error_from_attribute(_args: TokenStream, _input: TokenStream) -> TokenStream {
| ----------------------------------------------------------------------------------- in this expansion of procedural macro `#[error_from_attribute]`
...
LL | field: MissingType
| ^^^^^^^^^^^ not found in this scope
|
::: $DIR/span-from-proc-macro.rs:8:1
|
LL | #[error_from_attribute]
| ----------------------- in this macro invocation
```
Here, `MissingType` occurs inside the implementation of the proc-macro
`#[error_from_attribute]`. Previosuly, this would always result in a
span pointing at `#[error_from_attribute]`
This will make many proc-macro-related error message much more useful -
when a proc-macro generates code containing an error, users will get an
error message pointing directly at that code (within the macro
definition), instead of always getting a span pointing at the macro
invocation site.
This is implemented as follows:
* When a proc-macro crate is being *compiled*, it causes the `quote!`
macro to get run. This saves all of the sapns in the input to `quote!`
into the metadata of *the proc-macro-crate* (which we are currently
compiling). The `quote!` macro then expands to a call to
`proc_macro::Span::recover_proc_macro_span(id)`, where `id` is an
opaque identifier for the span in the crate metadata.
* When the same proc-macro crate is *run* (e.g. it is loaded from disk
and invoked by some consumer crate), the call to
`proc_macro::Span::recover_proc_macro_span` causes us to load the span
from the proc-macro crate's metadata. The proc-macro then produces a
`TokenStream` containing a `Span` pointing into the proc-macro crate
itself.
The recursive nature of 'quote!' can be difficult to understand at
first. The file `src/test/ui/proc-macro/quote-debug.stdout` shows
the output of the `quote!` macro, which should make this eaier to
understand.
This PR also supports custom quoting spans in custom quote macros (e.g.
the `quote` crate). All span quoting goes through the
`proc_macro::quote_span` method, which can be called by a custom quote
macro to perform span quoting. An example of this usage is provided in
`src/test/ui/proc-macro/auxiliary/custom-quote.rs`
Custom quoting currently has a few limitations:
In order to quote a span, we need to generate a call to
`proc_macro::Span::recover_proc_macro_span`. However, proc-macros
support renaming the `proc_macro` crate, so we can't simply hardcode
this path. Previously, the `quote_span` method used the path
`crate::Span` - however, this only works when it is called by the
builtin `quote!` macro in the same crate. To support being called from
arbitrary crates, we need access to the name of the `proc_macro` crate
to generate a path. This PR adds an additional argument to `quote_span`
to specify the name of the `proc_macro` crate. Howver, this feels kind
of hacky, and we may want to change this before stabilizing anything
quote-related.
Additionally, using `quote_span` currently requires enabling the
`proc_macro_internals` feature. The builtin `quote!` macro
has an `#[allow_internal_unstable]` attribute, but this won't work for
custom quote implementations. This will likely require some additional
tricks to apply `allow_internal_unstable` to the span of
`proc_macro::Span::recover_proc_macro_span`.
2020-08-02 23:52:16 +00:00
|
|
|
proc_macro_quoted_spans: Default::default(),
|
2022-09-02 08:29:40 +00:00
|
|
|
attr_id_generator: AttrIdGenerator::new(),
|
2019-10-09 01:23:10 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2021-10-02 17:15:45 +00:00
|
|
|
pub fn with_silent_emitter(fatal_note: Option<String>) -> Self {
|
2022-10-17 13:11:26 +00:00
|
|
|
let fallback_bundle = fallback_fluent_bundle(Vec::new(), false);
|
2020-02-22 14:07:05 +00:00
|
|
|
let sm = Lrc::new(SourceMap::new(FilePathMapping::empty()));
|
2022-03-26 07:27:43 +00:00
|
|
|
let fatal_handler =
|
2022-03-28 08:36:20 +00:00
|
|
|
Handler::with_tty_emitter(ColorConfig::Auto, false, None, None, None, fallback_bundle);
|
2021-10-02 17:15:45 +00:00
|
|
|
let handler = Handler::with_emitter(
|
|
|
|
false,
|
|
|
|
None,
|
|
|
|
Box::new(SilentEmitter { fatal_handler, fatal_note }),
|
|
|
|
);
|
2020-02-22 14:07:05 +00:00
|
|
|
ParseSess::with_span_handler(handler, sm)
|
2019-11-03 17:04:01 +00:00
|
|
|
}
|
|
|
|
|
2019-10-09 01:23:10 +00:00
|
|
|
#[inline]
|
|
|
|
pub fn source_map(&self) -> &SourceMap {
|
|
|
|
&self.source_map
|
|
|
|
}
|
|
|
|
|
2020-05-27 18:34:17 +00:00
|
|
|
pub fn clone_source_map(&self) -> Lrc<SourceMap> {
|
|
|
|
self.source_map.clone()
|
|
|
|
}
|
|
|
|
|
2019-10-09 01:23:10 +00:00
|
|
|
pub fn buffer_lint(
|
|
|
|
&self,
|
2020-01-05 08:40:16 +00:00
|
|
|
lint: &'static Lint,
|
2019-10-09 01:23:10 +00:00
|
|
|
span: impl Into<MultiSpan>,
|
2020-01-05 08:40:16 +00:00
|
|
|
node_id: NodeId,
|
2019-10-09 01:23:10 +00:00
|
|
|
msg: &str,
|
|
|
|
) {
|
|
|
|
self.buffered_lints.with_lock(|buffered_lints| {
|
|
|
|
buffered_lints.push(BufferedEarlyLint {
|
|
|
|
span: span.into(),
|
2020-01-05 08:40:16 +00:00
|
|
|
node_id,
|
2019-10-09 01:23:10 +00:00
|
|
|
msg: msg.into(),
|
2020-01-05 08:40:16 +00:00
|
|
|
lint_id: LintId::of(lint),
|
|
|
|
diagnostic: BuiltinLintDiagnostics::Normal,
|
2019-10-09 01:23:10 +00:00
|
|
|
});
|
|
|
|
});
|
|
|
|
}
|
|
|
|
|
2020-02-22 00:01:48 +00:00
|
|
|
pub fn buffer_lint_with_diagnostic(
|
|
|
|
&self,
|
|
|
|
lint: &'static Lint,
|
|
|
|
span: impl Into<MultiSpan>,
|
|
|
|
node_id: NodeId,
|
|
|
|
msg: &str,
|
|
|
|
diagnostic: BuiltinLintDiagnostics,
|
|
|
|
) {
|
|
|
|
self.buffered_lints.with_lock(|buffered_lints| {
|
|
|
|
buffered_lints.push(BufferedEarlyLint {
|
|
|
|
span: span.into(),
|
|
|
|
node_id,
|
|
|
|
msg: msg.into(),
|
|
|
|
lint_id: LintId::of(lint),
|
|
|
|
diagnostic,
|
|
|
|
});
|
|
|
|
});
|
|
|
|
}
|
|
|
|
|
Implement span quoting for proc-macros
This PR implements span quoting, allowing proc-macros to produce spans
pointing *into their own crate*. This is used by the unstable
`proc_macro::quote!` macro, allowing us to get error messages like this:
```
error[E0412]: cannot find type `MissingType` in this scope
--> $DIR/auxiliary/span-from-proc-macro.rs:37:20
|
LL | pub fn error_from_attribute(_args: TokenStream, _input: TokenStream) -> TokenStream {
| ----------------------------------------------------------------------------------- in this expansion of procedural macro `#[error_from_attribute]`
...
LL | field: MissingType
| ^^^^^^^^^^^ not found in this scope
|
::: $DIR/span-from-proc-macro.rs:8:1
|
LL | #[error_from_attribute]
| ----------------------- in this macro invocation
```
Here, `MissingType` occurs inside the implementation of the proc-macro
`#[error_from_attribute]`. Previosuly, this would always result in a
span pointing at `#[error_from_attribute]`
This will make many proc-macro-related error message much more useful -
when a proc-macro generates code containing an error, users will get an
error message pointing directly at that code (within the macro
definition), instead of always getting a span pointing at the macro
invocation site.
This is implemented as follows:
* When a proc-macro crate is being *compiled*, it causes the `quote!`
macro to get run. This saves all of the sapns in the input to `quote!`
into the metadata of *the proc-macro-crate* (which we are currently
compiling). The `quote!` macro then expands to a call to
`proc_macro::Span::recover_proc_macro_span(id)`, where `id` is an
opaque identifier for the span in the crate metadata.
* When the same proc-macro crate is *run* (e.g. it is loaded from disk
and invoked by some consumer crate), the call to
`proc_macro::Span::recover_proc_macro_span` causes us to load the span
from the proc-macro crate's metadata. The proc-macro then produces a
`TokenStream` containing a `Span` pointing into the proc-macro crate
itself.
The recursive nature of 'quote!' can be difficult to understand at
first. The file `src/test/ui/proc-macro/quote-debug.stdout` shows
the output of the `quote!` macro, which should make this eaier to
understand.
This PR also supports custom quoting spans in custom quote macros (e.g.
the `quote` crate). All span quoting goes through the
`proc_macro::quote_span` method, which can be called by a custom quote
macro to perform span quoting. An example of this usage is provided in
`src/test/ui/proc-macro/auxiliary/custom-quote.rs`
Custom quoting currently has a few limitations:
In order to quote a span, we need to generate a call to
`proc_macro::Span::recover_proc_macro_span`. However, proc-macros
support renaming the `proc_macro` crate, so we can't simply hardcode
this path. Previously, the `quote_span` method used the path
`crate::Span` - however, this only works when it is called by the
builtin `quote!` macro in the same crate. To support being called from
arbitrary crates, we need access to the name of the `proc_macro` crate
to generate a path. This PR adds an additional argument to `quote_span`
to specify the name of the `proc_macro` crate. Howver, this feels kind
of hacky, and we may want to change this before stabilizing anything
quote-related.
Additionally, using `quote_span` currently requires enabling the
`proc_macro_internals` feature. The builtin `quote!` macro
has an `#[allow_internal_unstable]` attribute, but this won't work for
custom quote implementations. This will likely require some additional
tricks to apply `allow_internal_unstable` to the span of
`proc_macro::Span::recover_proc_macro_span`.
2020-08-02 23:52:16 +00:00
|
|
|
pub fn save_proc_macro_span(&self, span: Span) -> usize {
|
2023-03-14 12:11:56 +00:00
|
|
|
self.proc_macro_quoted_spans.push(span)
|
Implement span quoting for proc-macros
This PR implements span quoting, allowing proc-macros to produce spans
pointing *into their own crate*. This is used by the unstable
`proc_macro::quote!` macro, allowing us to get error messages like this:
```
error[E0412]: cannot find type `MissingType` in this scope
--> $DIR/auxiliary/span-from-proc-macro.rs:37:20
|
LL | pub fn error_from_attribute(_args: TokenStream, _input: TokenStream) -> TokenStream {
| ----------------------------------------------------------------------------------- in this expansion of procedural macro `#[error_from_attribute]`
...
LL | field: MissingType
| ^^^^^^^^^^^ not found in this scope
|
::: $DIR/span-from-proc-macro.rs:8:1
|
LL | #[error_from_attribute]
| ----------------------- in this macro invocation
```
Here, `MissingType` occurs inside the implementation of the proc-macro
`#[error_from_attribute]`. Previosuly, this would always result in a
span pointing at `#[error_from_attribute]`
This will make many proc-macro-related error message much more useful -
when a proc-macro generates code containing an error, users will get an
error message pointing directly at that code (within the macro
definition), instead of always getting a span pointing at the macro
invocation site.
This is implemented as follows:
* When a proc-macro crate is being *compiled*, it causes the `quote!`
macro to get run. This saves all of the sapns in the input to `quote!`
into the metadata of *the proc-macro-crate* (which we are currently
compiling). The `quote!` macro then expands to a call to
`proc_macro::Span::recover_proc_macro_span(id)`, where `id` is an
opaque identifier for the span in the crate metadata.
* When the same proc-macro crate is *run* (e.g. it is loaded from disk
and invoked by some consumer crate), the call to
`proc_macro::Span::recover_proc_macro_span` causes us to load the span
from the proc-macro crate's metadata. The proc-macro then produces a
`TokenStream` containing a `Span` pointing into the proc-macro crate
itself.
The recursive nature of 'quote!' can be difficult to understand at
first. The file `src/test/ui/proc-macro/quote-debug.stdout` shows
the output of the `quote!` macro, which should make this eaier to
understand.
This PR also supports custom quoting spans in custom quote macros (e.g.
the `quote` crate). All span quoting goes through the
`proc_macro::quote_span` method, which can be called by a custom quote
macro to perform span quoting. An example of this usage is provided in
`src/test/ui/proc-macro/auxiliary/custom-quote.rs`
Custom quoting currently has a few limitations:
In order to quote a span, we need to generate a call to
`proc_macro::Span::recover_proc_macro_span`. However, proc-macros
support renaming the `proc_macro` crate, so we can't simply hardcode
this path. Previously, the `quote_span` method used the path
`crate::Span` - however, this only works when it is called by the
builtin `quote!` macro in the same crate. To support being called from
arbitrary crates, we need access to the name of the `proc_macro` crate
to generate a path. This PR adds an additional argument to `quote_span`
to specify the name of the `proc_macro` crate. Howver, this feels kind
of hacky, and we may want to change this before stabilizing anything
quote-related.
Additionally, using `quote_span` currently requires enabling the
`proc_macro_internals` feature. The builtin `quote!` macro
has an `#[allow_internal_unstable]` attribute, but this won't work for
custom quote implementations. This will likely require some additional
tricks to apply `allow_internal_unstable` to the span of
`proc_macro::Span::recover_proc_macro_span`.
2020-08-02 23:52:16 +00:00
|
|
|
}
|
|
|
|
|
2023-03-14 12:11:56 +00:00
|
|
|
pub fn proc_macro_quoted_spans(&self) -> impl Iterator<Item = (usize, Span)> + '_ {
|
|
|
|
// This is equivalent to `.iter().copied().enumerate()`, but that isn't possible for
|
|
|
|
// AppendOnlyVec, so we resort to this scheme.
|
2023-03-15 15:44:23 +00:00
|
|
|
self.proc_macro_quoted_spans.iter_enumerated()
|
Implement span quoting for proc-macros
This PR implements span quoting, allowing proc-macros to produce spans
pointing *into their own crate*. This is used by the unstable
`proc_macro::quote!` macro, allowing us to get error messages like this:
```
error[E0412]: cannot find type `MissingType` in this scope
--> $DIR/auxiliary/span-from-proc-macro.rs:37:20
|
LL | pub fn error_from_attribute(_args: TokenStream, _input: TokenStream) -> TokenStream {
| ----------------------------------------------------------------------------------- in this expansion of procedural macro `#[error_from_attribute]`
...
LL | field: MissingType
| ^^^^^^^^^^^ not found in this scope
|
::: $DIR/span-from-proc-macro.rs:8:1
|
LL | #[error_from_attribute]
| ----------------------- in this macro invocation
```
Here, `MissingType` occurs inside the implementation of the proc-macro
`#[error_from_attribute]`. Previosuly, this would always result in a
span pointing at `#[error_from_attribute]`
This will make many proc-macro-related error message much more useful -
when a proc-macro generates code containing an error, users will get an
error message pointing directly at that code (within the macro
definition), instead of always getting a span pointing at the macro
invocation site.
This is implemented as follows:
* When a proc-macro crate is being *compiled*, it causes the `quote!`
macro to get run. This saves all of the sapns in the input to `quote!`
into the metadata of *the proc-macro-crate* (which we are currently
compiling). The `quote!` macro then expands to a call to
`proc_macro::Span::recover_proc_macro_span(id)`, where `id` is an
opaque identifier for the span in the crate metadata.
* When the same proc-macro crate is *run* (e.g. it is loaded from disk
and invoked by some consumer crate), the call to
`proc_macro::Span::recover_proc_macro_span` causes us to load the span
from the proc-macro crate's metadata. The proc-macro then produces a
`TokenStream` containing a `Span` pointing into the proc-macro crate
itself.
The recursive nature of 'quote!' can be difficult to understand at
first. The file `src/test/ui/proc-macro/quote-debug.stdout` shows
the output of the `quote!` macro, which should make this eaier to
understand.
This PR also supports custom quoting spans in custom quote macros (e.g.
the `quote` crate). All span quoting goes through the
`proc_macro::quote_span` method, which can be called by a custom quote
macro to perform span quoting. An example of this usage is provided in
`src/test/ui/proc-macro/auxiliary/custom-quote.rs`
Custom quoting currently has a few limitations:
In order to quote a span, we need to generate a call to
`proc_macro::Span::recover_proc_macro_span`. However, proc-macros
support renaming the `proc_macro` crate, so we can't simply hardcode
this path. Previously, the `quote_span` method used the path
`crate::Span` - however, this only works when it is called by the
builtin `quote!` macro in the same crate. To support being called from
arbitrary crates, we need access to the name of the `proc_macro` crate
to generate a path. This PR adds an additional argument to `quote_span`
to specify the name of the `proc_macro` crate. Howver, this feels kind
of hacky, and we may want to change this before stabilizing anything
quote-related.
Additionally, using `quote_span` currently requires enabling the
`proc_macro_internals` feature. The builtin `quote!` macro
has an `#[allow_internal_unstable]` attribute, but this won't work for
custom quote implementations. This will likely require some additional
tricks to apply `allow_internal_unstable` to the span of
`proc_macro::Span::recover_proc_macro_span`.
2020-08-02 23:52:16 +00:00
|
|
|
}
|
2022-04-25 20:53:09 +00:00
|
|
|
|
2022-10-31 15:14:29 +00:00
|
|
|
#[track_caller]
|
2022-05-06 02:44:41 +00:00
|
|
|
pub fn create_err<'a>(
|
|
|
|
&'a self,
|
2022-09-18 15:45:41 +00:00
|
|
|
err: impl IntoDiagnostic<'a>,
|
2022-05-06 02:44:41 +00:00
|
|
|
) -> DiagnosticBuilder<'a, ErrorGuaranteed> {
|
2022-09-05 04:15:50 +00:00
|
|
|
err.into_diagnostic(&self.span_diagnostic)
|
2022-05-06 02:44:41 +00:00
|
|
|
}
|
|
|
|
|
2022-10-31 15:14:29 +00:00
|
|
|
#[track_caller]
|
2022-09-18 15:45:41 +00:00
|
|
|
pub fn emit_err<'a>(&'a self, err: impl IntoDiagnostic<'a>) -> ErrorGuaranteed {
|
2022-05-06 02:44:41 +00:00
|
|
|
self.create_err(err).emit()
|
|
|
|
}
|
|
|
|
|
2022-10-31 15:14:29 +00:00
|
|
|
#[track_caller]
|
2022-05-06 02:44:41 +00:00
|
|
|
pub fn create_warning<'a>(
|
|
|
|
&'a self,
|
2022-09-18 15:45:41 +00:00
|
|
|
warning: impl IntoDiagnostic<'a, ()>,
|
2022-05-06 02:44:41 +00:00
|
|
|
) -> DiagnosticBuilder<'a, ()> {
|
2022-09-05 04:15:50 +00:00
|
|
|
warning.into_diagnostic(&self.span_diagnostic)
|
2022-04-25 20:53:09 +00:00
|
|
|
}
|
|
|
|
|
2022-10-31 15:14:29 +00:00
|
|
|
#[track_caller]
|
2022-09-18 15:45:41 +00:00
|
|
|
pub fn emit_warning<'a>(&'a self, warning: impl IntoDiagnostic<'a, ()>) {
|
2022-05-06 02:44:41 +00:00
|
|
|
self.create_warning(warning).emit()
|
2022-04-25 20:53:09 +00:00
|
|
|
}
|
|
|
|
|
2022-09-01 10:40:43 +00:00
|
|
|
pub fn create_note<'a>(
|
|
|
|
&'a self,
|
|
|
|
note: impl IntoDiagnostic<'a, Noted>,
|
|
|
|
) -> DiagnosticBuilder<'a, Noted> {
|
|
|
|
note.into_diagnostic(&self.span_diagnostic)
|
|
|
|
}
|
|
|
|
|
|
|
|
pub fn emit_note<'a>(&'a self, note: impl IntoDiagnostic<'a, Noted>) -> Noted {
|
|
|
|
self.create_note(note).emit()
|
|
|
|
}
|
|
|
|
|
2022-08-18 12:20:50 +00:00
|
|
|
pub fn create_fatal<'a>(
|
|
|
|
&'a self,
|
2022-09-18 15:45:41 +00:00
|
|
|
fatal: impl IntoDiagnostic<'a, !>,
|
2022-08-18 12:20:50 +00:00
|
|
|
) -> DiagnosticBuilder<'a, !> {
|
2022-09-05 04:15:50 +00:00
|
|
|
fatal.into_diagnostic(&self.span_diagnostic)
|
2022-08-18 12:20:50 +00:00
|
|
|
}
|
|
|
|
|
2022-09-18 15:45:41 +00:00
|
|
|
pub fn emit_fatal<'a>(&'a self, fatal: impl IntoDiagnostic<'a, !>) -> ! {
|
2022-08-18 12:20:50 +00:00
|
|
|
self.create_fatal(fatal).emit()
|
|
|
|
}
|
|
|
|
|
2022-07-01 13:48:23 +00:00
|
|
|
#[rustc_lint_diagnostics]
|
2022-10-31 15:14:29 +00:00
|
|
|
#[track_caller]
|
2022-04-25 20:53:09 +00:00
|
|
|
pub fn struct_err(
|
|
|
|
&self,
|
|
|
|
msg: impl Into<DiagnosticMessage>,
|
|
|
|
) -> DiagnosticBuilder<'_, ErrorGuaranteed> {
|
|
|
|
self.span_diagnostic.struct_err(msg)
|
|
|
|
}
|
2022-04-25 21:49:53 +00:00
|
|
|
|
2022-07-01 13:48:23 +00:00
|
|
|
#[rustc_lint_diagnostics]
|
2022-04-25 21:49:53 +00:00
|
|
|
pub fn struct_warn(&self, msg: impl Into<DiagnosticMessage>) -> DiagnosticBuilder<'_, ()> {
|
|
|
|
self.span_diagnostic.struct_warn(msg)
|
|
|
|
}
|
2022-08-19 12:47:45 +00:00
|
|
|
|
2022-08-18 12:20:50 +00:00
|
|
|
#[rustc_lint_diagnostics]
|
|
|
|
pub fn struct_fatal(&self, msg: impl Into<DiagnosticMessage>) -> DiagnosticBuilder<'_, !> {
|
|
|
|
self.span_diagnostic.struct_fatal(msg)
|
|
|
|
}
|
|
|
|
|
2022-08-19 12:47:45 +00:00
|
|
|
#[rustc_lint_diagnostics]
|
|
|
|
pub fn struct_diagnostic<G: EmissionGuarantee>(
|
|
|
|
&self,
|
|
|
|
msg: impl Into<DiagnosticMessage>,
|
|
|
|
) -> DiagnosticBuilder<'_, G> {
|
|
|
|
self.span_diagnostic.struct_diagnostic(msg)
|
|
|
|
}
|
2019-10-09 01:23:10 +00:00
|
|
|
}
|