rust/tests/pretty/cast-lt.pp

#![feature(prelude_import)]
#![no_std]
#[prelude_import]
use ::std::prelude::rust_2015::*;
#[macro_use]
extern crate std;
// pretty-compare-only
// pretty-mode:expanded
// pp-exact:cast-lt.pp

macro_rules! negative { ($e:expr) => { $e < 0 } }

fn main() { (1 as i32) < 0; }
Added tests 2017-11-05 14:27:46 -06:00			`#![feature(prelude_import)]`
			`#![no_std]`
			`#[prelude_import]`
Update test/pretty output for edition preludes. 2021-02-17 08:52:31 -06:00			`use ::std::prelude::rust_2015::*;`
Added tests 2017-11-05 14:27:46 -06:00			`#[macro_use]`
fix expected output of pretty/cast-lt and issue-4264 tests 2018-07-11 18:16:27 -05:00			`extern crate std;`
Added tests 2017-11-05 14:27:46 -06:00			`// pretty-compare-only`
			`// pretty-mode:expanded`
			`// pp-exact:cast-lt.pp`

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-07 20:43:44 -05:00			`macro_rules! negative { ($e:expr) => { $e < 0 } }`
Added tests 2017-11-05 14:27:46 -06:00
			`fn main() { (1 as i32) < 0; }`