Bogdan Romanyuk
Bogdan Romanyuk
I'll be waiting. No matter how long it takes
here's debug stack trace ``` thread 1276 panic: reached unreachable code Analyzing repr.zig: repr.zig:main %5 = ret_type() node_offset:3:1 to :3:7 %6 = dbg_stmt(2, 5) %7 = decl_val("std") token_offset:4:23 to :4:26...
> The type printing changes look correct at least compared to clang. Did you compare with gcc? I did. But gcc issues diagnostics in a different way compared to clang....
Sorry for the delay, just didn't have enough time. Looks like CI failure is unrelated to this pr @Vexu
> This still doesn't cover every case: > > ```c > void foo(void) { > const int arr[2][2] = { 0, 1, 2, 3}; > arr[0][0] = 1; > }...
@Vexu can you take a look at it now?
@Vexu can you take a look at it now please?