00:00 <allochi> when I try to mutate the array, but not if I only read it.

00:01 <allochi> same original code, just comment the line `atest.value[0] = 0;` and you don't get bad access

00:08 <emekankurumeh[m]> i think you found a bug in zig

00:10 <allochi> Haha :D

00:10 <allochi> don't tell Andrew

00:10 <allochi> or we should

00:10 <allochi> what do you think? :D

00:14 <mikdusan> i’m still trying things out :)

00:16 <hryx> Hey andrewrk, I left a comment on this commit referencing an issue, but the issue doesn't show a link back: https://github.com/ziglang/zig/commit/3e9697bb35267973554155cedc2e593bd4519dd8#commitcomment-32955443

00:16 <hryx> I just wanted to confirm because the title is mismatched -- remove binary/octal but keep hex float literals, yeah?

02:38 <scientes> can I test whether a variable is comptime?

22:16 <wink_> I saw "zig cc" was added and thought I'd give it a try. I created helloworld.c which compiles with `clang helloworld.c` and runs. I tried `zig cc helloworld.c` and I got an error "/usr/include/stdio.h:33:10: fatal error: 'stddef.h' file not found". I see #2010 "add documentaiotn for using Zig as a C compiler" so no wonder there are no docs. Should

22:16 <wink_> I be able to compile a c program or may `zig cc` is just for non-main c files?

22:16 <andrewrk> zig cc is deprecated

22:16 <andrewrk> use --c-source

22:22 <andrewrk> actually I don't think zig cc is deprecated. it's just really low level, meant to be used by tools, not users directly

22:22 <andrewrk> zig build-exe --c-source helloworld.c --library c

22:32 <wink_> Bravo that worked, txs.

22:33 <andrewrk> you can also try some of the cross compiled libc targets, which you can see a listing of with `zig targets`

22:36 <wink_> Will it compile c++, just wondering?

22:36 <andrewrk> it can compile c++ but I haven't looked into the link dependencies of c++ yet

22:44 <wink_> got it, for grins I tried `$ ./build/bin/zig build-exe --c-source ../hw.cpp --library c` it failed 'stdio' file not found. and then output the `zig cc ...` command line that failed. I see why "cc" isn't designed for people, its 643 characters long :)

23:03 <scientes> hmmmm, *u21 can't cast to *u32. Why don't we guarantee that u17--u31 all have 32-bit alignment?

23:04 <scientes> or might u17-u24 be staggered into 3-bytes, with 1-bytes alignment I guess----maybe if I do Align(4) it could be allowed to up-cast?

23:42 <wilsonk> speaking of cross compiled libc targets...how long does it take others to build all the glibc targets? I didn't even build the musl libs yet, but all the glibc stuff took just over 3 hours on a massive 64 core AMD EPYC server!! The same machine compiles llvm/clang/lld/compiler-rt in 6m23s! Anyways, just letting others know glibcs will probably take a LONG time to compile :)

23:43 <scientes> did you run all the tests?

23:43 <scientes> oh yes

23:57 <wilsonk> just followed along running the scripts as per: https://github.com/ziglang/zig/wiki/Updating-libc-Headers

23:58 <wilsonk> which does seem to have a 'check' stage, so perhaps those are tests? Not totally sure