-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
'index out of bounds: the len is 0 but the index is 0' on match { } block #12116
Comments
For me, I'm getting this output:
Which isn't great because there are these 'module wasn't actually a module' lines in the output, so something definitely needs to get fixed here. I'm not getting the exact error you're describing, though, so this bug may be fixed on master. If you change
Which sounds like what you ran into (and should definitely be fixed!). The fix for this bug is to move the |
I received the same error when compiling the following socket server program (I have since fixed my code). compiler-specific error output:
code:
rustc -v:
uname -a:
|
I initially had that |
Some wrong code by me triggers this failure path on
|
I ran into this same issue when porting some code of mine to 0.10:
|
I just got this same error on Windows 7 with
The error I got was
And it appears the offending code was a match with out of order statements, similar to what @nathanisaac-s reported.
Hope this helps. |
fix suggestion error in [`useless_vec`] fixes: rust-lang#12101 --- changelog: fix suggestion error in [`useless_vec`] r+ `@matthiaskrgr` since they opened the issue?
I suspect this is malformed typing and pointer mgmt on my part, but regardless, the compiler throws an error rather then tells me I made one.
This is in an attempt to expand on the linked list from the docs.
error output:
Offending code:
uname -a
rust is at 0.9-2 on this box, with the binary pkg from the archlinux repos (should be vanilla compiled.)
The text was updated successfully, but these errors were encountered: