do not ICE in `fn forced_ambiguity` if we get an error by lcnr · Pull Request #1...
source link: https://github.com/rust-lang/rust/pull/123477
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
do not ICE in fn forced_ambiguity
if we get an error
#123477
Conversation
Contributor
see the comment. currently causing an ICE in typenum which we've been unable to minimize.
added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. WG-trait-system-refactor The Rustc Trait System Refactor Initiative
labels
Collaborator
Some changes occurred to the core trait solver cc @rust-lang/initiative-trait-system-refactor |
@bors r+ rollup I would like to revisit this before, e.g., stabilizing |
added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
labels
Member
We can probably reduce it a bit more, but it's not bad for There you go
(I didn't know how old the ICE was, but it's recent, from #122687) |
you're a wizard @lqd |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
No reviews
None yet
Successfully merging this pull request may close these issues.
None yet
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK