Tim (Theemathas) Chirananthavat
Tim (Theemathas) Chirananthavat
I did a cursory search manually for code on github that uses a pattern like `Foo { .. }`. It appears that there is some amount of people that uses...
```rust #![feature(super_let)] pub const C: *mut i32 = { super let mut x = 1; &raw mut x }; ``` Currently, this code fails to compile with the following error...
```rust #![feature(super_let)] pub const C: &i32 = { super let x = 1; &x }; ``` This code currently compiles fine.
Currently, in nightly, the following code compiles without unstable features, and it macro-expands to code that uses `super let` in the "top-level" of a const. ```rust use std::pin::{pin, Pin}; pub...
This ICE also occurs in const blocks, such as in the following code: ```rust #![feature(super_let)] fn main() { let _ = const { super let x = 1; &raw const...
Minimized: ```rust struct Thing; pub trait Every { type Assoc; } impl Every for Thing { type Assoc = T; } static I: ::Assoc = 3; ``` Error output ```...
Variant with a different ICE (`index out of bounds: the len is 0 but the index is 0`) ```rust struct Thing; pub trait Every { type Assoc; } impl Every...
How did the qroc crate suddenly start compiling in this crater run?
> it should probably only do so if `!std::thread::panicking()`; The situation is a bit more complicated. See https://github.com/rust-lang/rust/issues/143612
Bisected with `cargo bisect-rustc --start beta --end main --prompt -- asm` and manually inspecting the asm. ``` searched toolchains 75948c8bb3bd37f1e8ee20273a04edea4c1f84f8 through d427ddfe90367eaa6d2ed7bb8a16559f0230f47a ******************************************************************************** Regression in e9acbd99d384280874129fb7fa0da9faeae0d051 ******************************************************************************** Attempting to search...