about summary refs log tree commit diff
path: root/tests/mir-opt/lower_array_len.array_len_raw.NormalizeArrayLen.diff
diff options
context:
space:
mode:
authorAdam Bratschi-Kaye <ark.email@gmail.com>2021-11-03 23:57:46 +0100
committerAdam Bratschi-Kaye <ark.email@gmail.com>2021-11-10 21:29:50 +0100
commit0d54754ca73d8f370a902f605c94f4b588ded532 (patch)
tree6dbedff8944e276f7e128c98fc7bb272eda406f7 /tests/mir-opt/lower_array_len.array_len_raw.NormalizeArrayLen.diff
parent04f03a360ab8fef3d9c0ff84de2d39b8a196c717 (diff)
downloadrust-0d54754ca73d8f370a902f605c94f4b588ded532.tar.gz
rust-0d54754ca73d8f370a902f605c94f4b588ded532.zip
Handle pub tuple fields in tuple structs
The current implementation will throw a parser error for tuple structs
that contain a pub tuple field. For example,
```rust
struct Foo(pub (u32, u32));
```
is valid Rust, but rust-analyzer will throw a parser error.  This is
because the parens after `pub` is treated as a visibility context.
Allowing a tuple type to follow `pub` in the special case when we are
defining fields in a tuple struct can fix the issue.
Diffstat (limited to 'tests/mir-opt/lower_array_len.array_len_raw.NormalizeArrayLen.diff')
0 files changed, 0 insertions, 0 deletions