-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Compiler error "trying to take the sizing type of str, an unsized type" #16848
Comments
cc @nick29581 |
Similarly, just today (yes, I know the code should not compile, but it is the internal compiler error that is the issue): http://is.gd/tVfINu fn foo() -> Iterator<uint> {
range(0u, 10).map(|i| i*i) as Iterator<uint>
} |
Getting the same ICE.
Repro steps: check out Valloric/nailgun@3e1408e and run |
Another test case: #![allow(dead_code)]
trait A {}
fn foo<'a>() -> A + 'a { unimplemented!() }
fn main() {} Play pen: http://is.gd/kTRaZL |
+1 |
I tested it with latest rust and my problem seems fixed now. :) |
The playpen link from @mrmonday's post now produces the following output from rustc:
So the ICE seems to be gone; haven't yet tried it out my code though. |
I cannot repro the ICE on my own code anymore after upgrading to latest nightly. This might actually be fixed now. |
I'll close it then. I think there should be a new issue if there are other problems. |
I just compiled a project that compiled fine until tonight's nightly, and the backtrace looks very similar to the original poster's, so I'm putting it here (rather than opening a new issue)
|
@mikedilger It might be better to open it as a new issue for better visibility. |
yep. done. |
fix: handle attributes when typing curly bracket fix rust-lang#16848. When inserting a `{`, if it is identified that the front part of `expr` is `attr`, we consider it as inserting `{}` around the entire `expr` (excluding the attr part).
Hello,
I don't know if this is related to #16822 or not. I was following the example here http://doc.rust-lang.org/getopts/ and wanted to tweak it so the
program
is only the filename, not the whole path to it. So I started hacking around and extracted it into a function, which resulted into this error.I'm new to Rust, so… I'm doing silly things probably. :) Feel free to tell me.
Anyway this is not the "getopts" code, I wanted to isolate the problem. I also made the types explicit for illustration.
My system:
OS X 10.9.4
Thanks,
Ollie
The text was updated successfully, but these errors were encountered: