nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-12-02 11:44:28 +00:00
Code Issues Packages Projects Releases Wiki Activity
28628f3743
rust/tests/ui/proc-macro/nonterminal-token-hygiene.stdout

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

93 lines
3.7 KiB
Plaintext
Raw Normal View History

More detailed output for the nonterminal marking test
2020-11-05 21:36:30 +00:00
PRINT-BANG INPUT (DISPLAY): struct S;
PRINT-BANG INPUT (DEBUG): TokenStream [
Group {
delimiter: None,
stream: TokenStream [
Ident {
ident: "struct",
fix(test): improve sensitivity of hygene tests The change in 07f855d7817aa53af8adbb385407f6c2cacc2702 introduced a trailing numeral of some kind after the `extern crate compiler_builtins`, which appears to have caused at least two false negatives (654b924 and 657fd24). Instead, this change normalizes the test output to ignore the number (of symbols rustc recognizes?) to avoid needing to re-`--bless` these two tests for unrelated changes.
2023-07-29 21:44:17 +00:00
span: $DIR/nonterminal-token-hygiene.rs:32:5: 32:11 (#4),
More detailed output for the nonterminal marking test
2020-11-05 21:36:30 +00:00
},
Ident {
ident: "S",
fix(test): improve sensitivity of hygene tests The change in 07f855d7817aa53af8adbb385407f6c2cacc2702 introduced a trailing numeral of some kind after the `extern crate compiler_builtins`, which appears to have caused at least two false negatives (654b924 and 657fd24). Instead, this change normalizes the test output to ignore the number (of symbols rustc recognizes?) to avoid needing to re-`--bless` these two tests for unrelated changes.
2023-07-29 21:44:17 +00:00
span: $DIR/nonterminal-token-hygiene.rs:32:12: 32:13 (#4),
More detailed output for the nonterminal marking test
2020-11-05 21:36:30 +00:00
},
Punct {
ch: ';',
spacing: Alone,
fix(test): improve sensitivity of hygene tests The change in 07f855d7817aa53af8adbb385407f6c2cacc2702 introduced a trailing numeral of some kind after the `extern crate compiler_builtins`, which appears to have caused at least two false negatives (654b924 and 657fd24). Instead, this change normalizes the test output to ignore the number (of symbols rustc recognizes?) to avoid needing to re-`--bless` these two tests for unrelated changes.
2023-07-29 21:44:17 +00:00
span: $DIR/nonterminal-token-hygiene.rs:32:13: 32:14 (#4),
More detailed output for the nonterminal marking test
2020-11-05 21:36:30 +00:00
},
],
fix(test): improve sensitivity of hygene tests The change in 07f855d7817aa53af8adbb385407f6c2cacc2702 introduced a trailing numeral of some kind after the `extern crate compiler_builtins`, which appears to have caused at least two false negatives (654b924 and 657fd24). Instead, this change normalizes the test output to ignore the number (of symbols rustc recognizes?) to avoid needing to re-`--bless` these two tests for unrelated changes.
2023-07-29 21:44:17 +00:00
span: $DIR/nonterminal-token-hygiene.rs:22:27: 22:32 (#5),
More detailed output for the nonterminal marking test
2020-11-05 21:36:30 +00:00
},
]
#![feature /* 0#0 */(prelude_import)]
#![no_std /* 0#0 */]
// Make sure that marks from declarative macros are applied to tokens in nonterminal.
//@ check-pass
//@ compile-flags: -Z span-debug -Z macro-backtrace -Z unpretty=expanded,hygiene
//@ compile-flags: -Z trim-diagnostic-paths=no
fix(test): improve sensitivity of hygene tests The change in 07f855d7817aa53af8adbb385407f6c2cacc2702 introduced a trailing numeral of some kind after the `extern crate compiler_builtins`, which appears to have caused at least two false negatives (654b924 and 657fd24). Instead, this change normalizes the test output to ignore the number (of symbols rustc recognizes?) to avoid needing to re-`--bless` these two tests for unrelated changes.
2023-07-29 21:44:17 +00:00
// ignore-tidy-linelength
Always use a colon in `//@ normalize-*:` headers
2024-06-21 05:15:36 +00:00
//@ normalize-stdout-test: "\d+#" -> "0#"
//@ normalize-stdout-test: "expn\d{3,}" -> "expnNNN"
//@ normalize-stdout-test: "extern crate compiler_builtins /\* \d+ \*/" -> "extern crate compiler_builtins /* NNN */"
More detailed output for the nonterminal marking test
2020-11-05 21:36:30 +00:00
//@ aux-build:test-macros.rs
#![feature /* 0#0 */(decl_macro)]
#![no_std /* 0#0 */]
#[prelude_import /* 0#1 */]
Update test output for edition preludes.
2021-02-17 14:52:31 +00:00
use ::core /* 0#1 */::prelude /* 0#1 */::rust_2015 /* 0#1 */::*;
More detailed output for the nonterminal marking test
2020-11-05 21:36:30 +00:00
#[macro_use /* 0#1 */]
extern crate core /* 0#2 */;
fix(test): improve sensitivity of hygene tests The change in 07f855d7817aa53af8adbb385407f6c2cacc2702 introduced a trailing numeral of some kind after the `extern crate compiler_builtins`, which appears to have caused at least two false negatives (654b924 and 657fd24). Instead, this change normalizes the test output to ignore the number (of symbols rustc recognizes?) to avoid needing to re-`--bless` these two tests for unrelated changes.
2023-07-29 21:44:17 +00:00
extern crate compiler_builtins /* NNN */ as _ /* 0#2 */;
More detailed output for the nonterminal marking test
2020-11-05 21:36:30 +00:00
// Don't load unnecessary hygiene information from std
extern crate std /* 0#0 */;
#[macro_use /* 0#0 */]
extern crate test_macros /* 0#0 */;
macro_rules! outer
/*
0#0
*/ {
Improve `print_tts` by changing `tokenstream::Spacing`. `tokenstream::Spacing` appears on all `TokenTree::Token` instances, both punct and non-punct. Its current usage: - `Joint` means "can join with the next token *and* that token is a punct". - `Alone` means "cannot join with the next token *or* can join with the next token but that token is not a punct". The fact that `Alone` is used for two different cases is awkward. This commit augments `tokenstream::Spacing` with a new variant `JointHidden`, resulting in: - `Joint` means "can join with the next token *and* that token is a punct". - `JointHidden` means "can join with the next token *and* that token is a not a punct". - `Alone` means "cannot join with the next token". This *drastically* improves the output of `print_tts`. For example, this: ``` stringify!(let a: Vec<u32> = vec![];) ``` currently produces this string: ``` let a : Vec < u32 > = vec! [] ; ``` With this PR, it now produces this string: ``` let a: Vec<u32> = vec![] ; ``` (The space after the `]` is because `TokenTree::Delimited` currently doesn't have spacing information. The subsequent commit fixes this.) The new `print_tts` doesn't replicate original code perfectly. E.g. multiple space characters will be condensed into a single space character. But it's much improved. `print_tts` still produces the old, uglier output for code produced by proc macros. Because we have to translate the generated code from `proc_macro::Spacing` to the more expressive `token::Spacing`, which results in too much `proc_macro::Along` usage and no `proc_macro::JointHidden` usage. So `space_between` still exists and is used by `print_tts` in conjunction with the `Spacing` field. This change will also help with the removal of `Token::Interpolated`. Currently interpolated tokens are pretty-printed nicely via AST pretty printing. `Token::Interpolated` removal will mean they get printed with `print_tts`. Without this change, that would result in much uglier output for code produced by decl macro expansions. With this change, AST pretty printing and `print_tts` produce similar results. The commit also tweaks the comments on `proc_macro::Spacing`. In particular, it refers to "compound tokens" rather than "multi-char operators" because lifetimes aren't operators.
2023-08-08 01:43:44 +00:00
($item:item) =>
More detailed output for the nonterminal marking test
2020-11-05 21:36:30 +00:00
{
Add spacing information to delimiters. This is an extension of the previous commit. It means the output of something like this: ``` stringify!(let a: Vec<u32> = vec![];) ``` goes from this: ``` let a: Vec<u32> = vec![] ; ``` With this PR, it now produces this string: ``` let a: Vec<u32> = vec![]; ```
2023-10-12 04:36:14 +00:00
macro inner() { print_bang! { $item } } inner!();
More detailed output for the nonterminal marking test
2020-11-05 21:36:30 +00:00
Add spacing information to delimiters. This is an extension of the previous commit. It means the output of something like this: ``` stringify!(let a: Vec<u32> = vec![];) ``` goes from this: ``` let a: Vec<u32> = vec![] ; ``` With this PR, it now produces this string: ``` let a: Vec<u32> = vec![]; ```
2023-10-12 04:36:14 +00:00
};
More detailed output for the nonterminal marking test
2020-11-05 21:36:30 +00:00
}
struct S /* 0#0 */;
Hide `compiler_builtins` in the prelude This crate is a private implementation detail. We only need to insert it into the crate graph for linking and should not expose any of its public API. Fixes #113533
2023-07-10 22:16:28 +00:00
macro inner /* 0#3 */ { () => { print_bang! { struct S; } } }
More detailed output for the nonterminal marking test
2020-11-05 21:36:30 +00:00
Hide `compiler_builtins` in the prelude This crate is a private implementation detail. We only need to insert it into the crate graph for linking and should not expose any of its public API. Fixes #113533
2023-07-10 22:16:28 +00:00
struct S /* 0#4 */;
More detailed output for the nonterminal marking test
2020-11-05 21:36:30 +00:00
// OK, not a duplicate definition of `S`
Pretty print empty blocks as {}
2021-12-01 19:45:14 +00:00
fn main /* 0#0 */() {}
More detailed output for the nonterminal marking test
2020-11-05 21:36:30 +00:00
/*
Expansions:
Use LocalExpnId where possible.
2021-06-25 18:43:04 +00:00
crate0::{{expn0}}: parent: crate0::{{expn0}}, call_site_ctxt: #0, def_site_ctxt: #0, kind: Root
crate0::{{expn1}}: parent: crate0::{{expn0}}, call_site_ctxt: #0, def_site_ctxt: #0, kind: AstPass(StdImports)
crate0::{{expn2}}: parent: crate0::{{expn0}}, call_site_ctxt: #0, def_site_ctxt: #0, kind: Macro(Bang, "outer")
Hide `compiler_builtins` in the prelude This crate is a private implementation detail. We only need to insert it into the crate graph for linking and should not expose any of its public API. Fixes #113533
2023-07-10 22:16:28 +00:00
crate0::{{expn3}}: parent: crate0::{{expn2}}, call_site_ctxt: #3, def_site_ctxt: #3, kind: Macro(Bang, "inner")
crate0::{{expn4}}: parent: crate0::{{expn3}}, call_site_ctxt: #5, def_site_ctxt: #0, kind: Macro(Bang, "print_bang")
Replace some usage of `#[rustc_on_unimplemented]` with `#[diagnostic::on_unimplemented]` This commit replaces those `#[rustc_on_unimplemented]` attributes with their equivalent `#[diagnostic::on_unimplemented]` where this is supported (So no filter or any extended option)
2023-12-22 13:30:12 +00:00
crate1::{{expnNNN}}: parent: crate0::{{expn0}}, call_site_ctxt: #0, def_site_ctxt: #0, kind: Macro(Attr, "diagnostic::on_unimplemented")
crate1::{{expnNNN}}: parent: crate0::{{expn0}}, call_site_ctxt: #0, def_site_ctxt: #0, kind: Macro(Attr, "diagnostic::on_unimplemented")
crate1::{{expnNNN}}: parent: crate0::{{expn0}}, call_site_ctxt: #0, def_site_ctxt: #0, kind: Macro(Attr, "diagnostic::on_unimplemented")
Handle cross-crate module `ExpnId`s consistently - Always use the ExpnId serialized to `tables` - Use the Id for traits and enums from other crates in resolution.
2021-10-21 21:06:40 +00:00
crate1::{{expnNNN}}: parent: crate0::{{expn0}}, call_site_ctxt: #0, def_site_ctxt: #0, kind: Macro(Attr, "derive")
crate1::{{expnNNN}}: parent: crate0::{{expn0}}, call_site_ctxt: #0, def_site_ctxt: #0, kind: Macro(Attr, "derive")
resolve: Cache module loading for all foreign modules It was previously cached for modules loaded from `fn get_module`, but not for modules loaded from `fn build_reduced_graph_for_external_crate_res`. This also makes all foreign modules use their real parent, span and expansion instead of possibly a parent/span/expansion of their reexport. An ICE happening on attempt to decode expansions for foreign enums and traits is avoided. Also local enums and traits are now added to the module map.
2021-09-24 23:27:00 +00:00
crate1::{{expnNNN}}: parent: crate0::{{expn0}}, call_site_ctxt: #0, def_site_ctxt: #0, kind: Macro(Bang, "include")
More detailed output for the nonterminal marking test
2020-11-05 21:36:30 +00:00
SyntaxContexts:
Use LocalExpnId where possible.
2021-06-25 18:43:04 +00:00
#0: parent: #0, outer_mark: (crate0::{{expn0}}, Opaque)
#1: parent: #0, outer_mark: (crate0::{{expn1}}, Opaque)
#2: parent: #0, outer_mark: (crate0::{{expn1}}, Transparent)
Hide `compiler_builtins` in the prelude This crate is a private implementation detail. We only need to insert it into the crate graph for linking and should not expose any of its public API. Fixes #113533
2023-07-10 22:16:28 +00:00
#3: parent: #0, outer_mark: (crate0::{{expn2}}, SemiTransparent)
#4: parent: #0, outer_mark: (crate0::{{expn3}}, Opaque)
#5: parent: #3, outer_mark: (crate0::{{expn3}}, Opaque)
#6: parent: #0, outer_mark: (crate0::{{expn4}}, Opaque)
#7: parent: #5, outer_mark: (crate0::{{expn4}}, Transparent)
#8: parent: #4, outer_mark: (crate0::{{expn4}}, SemiTransparent)
More detailed output for the nonterminal marking test
2020-11-05 21:36:30 +00:00
*/
Reference in New Issue Copy Permalink