-
I was poking around in logs and found this panic, which unfortunately would take down the server. Unfortunately I don't have the precise text that was being rendered offhand yt
```
Sep 02 17:50:49…
-
I'm pretty sure this bug is somehow related to the `impl trait` feature as I was implementing a fn that returns an `impl std::iter::Iterator` for some struct `Node`. It also *seems* related to lifetim…
-
```Rust
use std::iter;
fn silly(it: I) {
silly(it.chain(iter::empty()))
}
fn main() {
println!("Start");
silly(iter::empty());
println!("Done");
}
```
This code causes…
-
```rust
// test.rs
pub fn main() {
let bytes: [u8; 8] = unsafe { ::std::mem::transmute(0u64) };
let _: &[u8] = &bytes;
}
```
```
$ cargo run --bin miri -- test.rs
Finished dev…
-
NB: Part of the [roadmap issue on incremental compilation](https://github.com/rust-lang/rust-roadmap/issues/4).
**Newer writeup:**
The plan is to change how we hash metadata. Instead of hashing …
-
In Servo with rustc 1.19.0-nightly (0ed1ec9f9 2017-05-18), with incremental compilation enabled. (To reproduce, copy `servobuild.example` to `.servobuild` and change `incremental = false` to `incremen…
-
Looks like a straight-up bug and I don't see why it would happen.
```
match (ppm, opt_uii) {
- (PpmSource(s), _) => {
- // Silently ignores an identified node.
- let…
-
Following code causes internal compiler error on nighly:
```rust
pub struct A {
_item: T,
}
impl A {
fn foo(&self) {
let _: fn() = || {};
}
}
fn main() {
let a =…
-
Regression after https://github.com/rust-lang/rust/pull/40224
The MIR of the following code used to include an `unreachable` statement
```rust
#![feature(never_type)]
#![allow(unreachable_code…
-
```
DEBUG:rustc::dep_graph: About to start task CollectItem(DefId { krate: 0, node: DefIndex(2)error: internal compiler error: unexpected panic
note: the compiler unexpectedly panicked. this is a bug.…