diff options
| author | Jakub Bukaj <jakub@jakub.cc> | 2014-11-19 22:41:05 +0100 |
|---|---|---|
| committer | Jakub Bukaj <jakub@jakub.cc> | 2014-11-19 22:41:05 +0100 |
| commit | f71b852d3865e878b953cb280724fb2ce1203103 (patch) | |
| tree | 4cf08dabab8901fcbac433e2d3f964abeaab2d94 /src/libstd/sys/unix/stack_overflow.rs | |
| parent | 00ffcca0164504ecae8453750a053e2b7206264a (diff) | |
| parent | a11078f8c3a69f0d4ea20ca10aaf96622770615b (diff) | |
| download | rust-f71b852d3865e878b953cb280724fb2ce1203103.tar.gz rust-f71b852d3865e878b953cb280724fb2ce1203103.zip | |
rollup merge of #19103: huonw/literal-suffixes
Futureproof Rust for fancier suffixed literals. The Rust compiler tokenises a literal followed immediately (no whitespace) by an identifier as a single token: (for example) the text sequences `"foo"bar`, `1baz` and `1u1024` are now a single token rather than the pairs `"foo"` `bar`, `1` `baz` and `1u` `1024` respectively.
The compiler rejects all such suffixes in the parser, except for the 12 numeric suffixes we have now.
I'm fairly sure this will affect very few programs, since it's not currently legal to have `<literal><identifier>` in a Rust program, except in a macro invocation. Any macro invocation relying on this behaviour can simply separate the two tokens with whitespace: `foo!("bar"baz)` becomes `foo!("bar" baz)`.
This implements [RFC 463](https://github.com/rust-lang/rfcs/blob/master/text/0463-future-proof-literal-suffixes.md), and so closes https://github.com/rust-lang/rust/issues/19088.
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions