Exponential parse time involving maybe_suggest_struct_literal · Issue #105067 · rust-lang/rust (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Description

Code

fn main() { 0 & { x: y & { x: y & { x: y & { x: y & { x: y & { x: y & { x: y & { x: y & { x: y & { x: y & { x: y & { x: y & { x: y & { x: y & { x: y & { x: y & { x: y & { x: y & { x: y & { x: y & { x: y & {

Where it's slow

According to -Z time-passes, the slow pass is parse_crate.

sample-head.txt

maybe_suggest_struct_literal repeatedly on the stack is sus.

Regression

Regression in nightly-2020-10-09, most likely from #75470, which added the function maybe_suggest_struct_literal (@estebank)

Version

rustc 1.67.0-nightly (1eb62b123 2022-11-27)
binary: rustc
commit-hash: 1eb62b1235fd77200e6bd967d70e83c0f2497233
commit-date: 2022-11-27
host: x86_64-apple-darwin
release: 1.67.0-nightly
LLVM version: 15.0.4

@rustbot label +I-compiletime