Skip to content

internal error: entered unreachable code: parse_dot_or_call_expr_with_ shouldn't produce this #70552

Closed
@dwrensha

Description

@dwrensha

I'm seeing an internal compiler error on the following input (found by fuzz-rustc):

type T = [(String, [String; u:b ()(:)])];
$ rustc main.rs
error: expected expression, found `:`
 --> main.rs:1:36
  |
1 | type T = [(String, [String; u:b ()(:)])];
  |                                    ^ expected expression

thread 'rustc' panicked at 'internal error: entered unreachable code: parse_dot_or_call_expr_with_ shouldn't produce this', src/librustc_parse/parser/expr.rs:641:26
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports

note: rustc 1.44.0-nightly (699f83f52 2020-03-29) running on x86_64-unknown-linux-gnu

error: aborting due to previous error

Metadata

Metadata

Assignees

Labels

A-diagnosticsArea: Messages for errors, warnings, and lintsA-parserArea: The lexing & parsing of Rust source code to an ASTI-ICEIssue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️P-mediumMedium priorityT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.regression-from-stable-to-betaPerformance or correctness regression from stable to beta.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions