-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Panic at 'index out of bounds: the len is 2 but the index is 2' #10179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I saw a similar issue with our in-house codebase. The error message looked identical apart from the len/index values (1/1 for me). FWIW I was able to work around the issue by downgrading the rust-analyzer vscode extension to v0.2.710. All newer versions seem to suffer from this issue. |
Likely a duplicate of #10046 |
Lazy minimization: use bitvec::array::BitArray;
fn main() {
let mut holes = BitArray::default();
holes.set(0, true);
} |
Seems like the same case as mine then. |
Should fix rust-lang#10090, rust-lang#10046, rust-lang#10179. This is only a workaround, but the proper fix requires some bigger refactoring (also related to fixing rust-lang#10058), and this at least prevents the crash.
Should be fixed with the next release. |
Thanks! |
When editing a pacticular project I keep getting this panic message from RA (b73b321 2021-09-06 stable, VS Code, Arch Linux). Here is the error output in VS code: <gist>.
Repro:
The text was updated successfully, but these errors were encountered: