forked from rust-lang/rust
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Rollup merge of rust-lang#113803 - compiler-errors:const-interp-block…
…, r=fee1-dead Fix inline_const with interpolated block Interpolation already worked when we had a `const $block` that wasn't a statement expr: ``` fn foo() { let _ = const $block; } ``` But it was failing when the const block was in statement expr position: ``` fn foo() { const $block; } ``` ... because of a bug in a check for const items. This fixes that. --- cc rust-lang#112953 (comment), though I don't think this requires an FCP since it's already supported in exprs and seems to me to be fully a parser bug.
- Loading branch information
Showing
2 changed files
with
34 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
// check-pass | ||
|
||
#![feature(inline_const)] | ||
|
||
// This used to be unsupported since the parser first tries to check if we have | ||
// any nested items, and then checks for statements (and expressions). The heuristic | ||
// that we were using to detect the beginning of a const item was incorrect, so | ||
// this used to fail. | ||
macro_rules! m { | ||
($b:block) => { | ||
fn foo() { | ||
const $b | ||
} | ||
} | ||
} | ||
|
||
// This has worked since inline-consts were implemented, since the position that | ||
// the const block is located at doesn't support nested items (e.g. because | ||
// `let x = const X: u32 = 1;` is invalid), so there's no ambiguity parsing the | ||
// inline const. | ||
macro_rules! m2 { | ||
($b:block) => { | ||
fn foo2() { | ||
let _ = const $b; | ||
} | ||
} | ||
} | ||
|
||
m!({}); | ||
m2!({}); | ||
|
||
fn main() {} |