Open rix0rrr opened 2 weeks ago
I'm not quite sure how this code can cause that panic... must be due to inlining?
fn fold_free_var_lifetime(
&mut self,
bound_var: BoundVar,
outer_binder: DebruijnIndex,
) -> Lifetime<I> {
assert_eq!(bound_var.debruijn, DebruijnIndex::INNERMOST);
let l = self.at(bound_var.index);
let l = l.assert_lifetime_ref(TypeFolder::interner(self));
l.clone()
.shifted_in_from(TypeFolder::interner(self), outer_binder)
}
I guess #17160 didn't fix this one CC @dfireBird.
Yeah, this and some stracktraces presented in #17080 seem same. I'm currently trying to fix that issue.
Hello, A fix was pushed with PR #17190 and it was released as part of today's release (version number: 0.4.1949). Can you please test it and report whether the issue is fixed for you or not? Thanks.
Hard to say, I'm now running into this: https://github.com/rust-lang/rust-analyzer/issues/16376
EDIT: well wait. On the beta channel so far it seems to be better, but I've only given it a couple minutes so far.
The following panic happens to me in both release version and pre-release version in VSCode as soon as the analyzer needs to autocomplete anything, and nearly makes it impossible to use:
rust-analyzer version:
Both of these:
rustc version: rustc 1.75.0 (82e1608df 2023-12-21)
editor or extension:
Both of these:
relevant settings: Nothing special
code snippet to reproduce: Happens on a large proprietary project, unsure what's triggering it.