Compiling with debug logging is never end. #11701
Conversation
|
I'm going to guess that the vector doesn't have infinite length, it's just very large. |
|
Actually, length of the vector is 34995047. Is it normal? Compiling with debug logging emits over 4GB output. so I have commented out line 220, 225 in line 220 : and finally build successfully in a short time. |
|
Pull requests are welcome! This is just dumping a few megabytes of metadata which gets inflated because it prints a few bytes per byte of metadata. Nothing worrisome here, just a stray debug statement that should be removed. |
|
Oh wow I was quite confused, I had no idea I was commenting on a pull request before, sorry about that! |
|
@alexcrichton this was an issue. It was "upgraded" to a PR, which, apparently, can be done via the API: http://opensoul.org/2012/11/09/convert-a-github-issue-into-a-pull-request/ |
|
My mind was just blown. |
When there is `println!` macro in the code, compiling is never end.
```rust
// print.rs
fn main() {
println!("Hello!");
}
```
```bash
$ RUST_LOG=rustc rustc print.rs
```
And this is a part of output from stderr.
```bash
# ...
Looking up syntax::ast::DefId{crate: 1u32, node: 176234u32}
looking up syntax::ast::DefId{crate: 1u32, node: 176235u32} : extra::ebml::Doc<>{data: &[168u8, 16u8, 0u8, 0u8, 16u8, 51u8, 101u8, 53u8, 97u8, 101u8, 98u8, 56u8, 51u8, 55u8, 97u8, 101u8, 49u8, 54u8, 50u8
# ...
# vector which has infinite length.
```
* note : rust 0.9, 0.10-pre
Implement location link for type inlay hints fix rust-lang#11701 This actually doesn't work due a problem in vscode: microsoft/vscode#167564
…Jarcho Use multiple pushes in `vec_init_then_push` example Makes the perf argument clearer, since a single push doesn't have unnecessary allocations compared to `vec![x]` changelog: none
When there is
println!macro in the code, compiling is never end.And this is a part of output from stderr.