Skip to content

ICE: "vtables missing where they are needed" with autoderef #13042

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
alexcrichton opened this issue Mar 20, 2014 · 1 comment
Closed

ICE: "vtables missing where they are needed" with autoderef #13042

alexcrichton opened this issue Mar 20, 2014 · 1 comment
Labels
I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️

Comments

@alexcrichton
Copy link
Member

I haven't quite gotten a minimized test case yet, but I have seen ICEs related to this when you have a Deref implementation that has trait bounds on some type parameters. I'm creating a placeholder bug so I can tag some FIXME's here and there. I'll try to get a reduced test case soon.

@eddyb says he knows what's going on here, so I haven't tried too hard to minimize this just yet.

@emberian
Copy link
Member

The dreaded missing vtable ICE. I thought we'd wiped it out. blames @eddyb

bors added a commit that referenced this issue Mar 22, 2014
This commit removes the `get()` method from `Ref` and `RefMut` in favor of the `*` operator, and removes all usage of the `deref()` function manually from rustc, favoring using `*` instead.

Some of the code is a little wacky, but that's due to either #13044 or #13042
@bors bors closed this as completed in 75d7d52 Mar 23, 2014
flip1995 pushed a commit to flip1995/rust that referenced this issue Jul 11, 2024
`almost_complete_range`: Delay suggestion creation.

Does less work when the lint doesn't trigger.

changelog: none
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
Projects
None yet
Development

No branches or pull requests

2 participants