-
Notifications
You must be signed in to change notification settings - Fork 13.9k
Open
Labels
C-bugCategory: This is a bug.Category: This is a bug.I-hangIssue: The compiler never terminates, due to infinite loops, deadlock, livelock, etc.Issue: The compiler never terminates, due to infinite loops, deadlock, livelock, etc.P-mediumMedium priorityMedium priorityT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.regression-from-stable-to-stablePerformance or correctness regression from one stable version to another.Performance or correctness regression from one stable version to another.
Description
Hi!
The crate located here:
https://github.com/krtab/diff/releases/tag/infiloop at commit c7d13ab3473147785a7f35f97461d828e9421fd2
Makes cargo/rustc go to an infinite loop. (I tried for 4 hours, it went up to 80GB of RAM).
git clone 'https://github.com/krtab/diff.git'
cd diff
git checkout c7d13ab3473147785a7f35f97461d828e9421fd2
cargo checkGiven the amount of type-level black-magic, I'd wager there is some cycle/infinite recursion when trying to type-check.
Meta
rustc --version --verbose:
rustc 1.49.0 (e1884a8e3 2020-12-29)
binary: rustc
commit-hash: e1884a8e3c3e813aada8254edfa120e85bf5ffca
commit-date: 2020-12-29
host: x86_64-unknown-linux-gnu
release: 1.49.0
I have also tried 1.50-beta and today's nightly, and ask someone to test 1.48, to no avail.
Given that it doesn't finish, there is no backtrace.
Let me know how I can help!
hellow554 and tesujirgrunbla
Metadata
Metadata
Assignees
Labels
C-bugCategory: This is a bug.Category: This is a bug.I-hangIssue: The compiler never terminates, due to infinite loops, deadlock, livelock, etc.Issue: The compiler never terminates, due to infinite loops, deadlock, livelock, etc.P-mediumMedium priorityMedium priorityT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.regression-from-stable-to-stablePerformance or correctness regression from one stable version to another.Performance or correctness regression from one stable version to another.