01:23 <ar1a> so what's the difference between zig and similar languages like rust?

01:24 <andrewrk> https://github.com/ziglang/zig/wiki/Why-Zig-When-There-is-Already-CPP,-D,-and-Rust%3F

01:24 <ar1a> wow handy

01:31 <ottidmes> andrewrk: interesting language! BTW maybe add https:// in front of ziglang.org in your topic line, to trigger the open link feature in most IRC clients

01:34 <ar1a> ^

01:35 <ottidmes> thanks!

01:36 <andrewrk> thanks for the suggestion

01:37 <ottidmes> I should probably look into the wiki more, but now that I am here, how does Zig compare to Rust in terms of safety. I guess Zig targets lower level use cases, and so safety is harder to guarantee?

01:38 <andrewrk> ottidmes, zig does not have rust's `unsafe` concept and it does not have a borrow checker. however in some ways zig can be safer than rust: https://andrewkelley.me/post/unsafe-zig-safer-than-unsafe-rust.html

01:39 <andrewrk> zig relies heavily on using debug builds to detect undefined behavior: https://ziglang.org/documentation/master/#Undefined-Behavior

01:40 <andrewrk> and then when you're ready to release, you have some release options: https://ziglang.org/documentation/master/#Build-Mode

01:41 <andrewrk> some kinds of undefined behavior zig is not able to detect, even at runtime. I plan on creating an exhaustive list of these: https://github.com/ziglang/zig/issues/1966 and hopefully many of the items in the list can have runtime checks, but there will be some impossible cases of course

01:41 <andrewrk> I'll be back in an hour or so

01:42 <ottidmes> seems like a good choice, focus on correctness during development, and focus on performance for releases

02:25 <gamester> I really like the zig fmt and parse error notifications when I save in vim, but I'm utterly confused as to how it's happening?

02:26 <gamester> I see now, it's coming from andrew's zig.vim project which I haven't updated in forever (iirc)

03:52 <andrewrk> gamester, I believe what happened is that it was using `zig fmt` which was erroring out, but as of a recent version of zig, `zig fmt` works in stage1

13:38 <gamester> andrewrk: typo "sytsem" in docs

13:51 <andrewrk> gamester, fixed. also I fixed the issue you reported with @bitCast

13:51 <andrewrk> new binary download should be available within 2 hours

13:52 <gamester> awesome

13:54 <andrewrk> I fixed all the known bugs having to do with packed structs (except an issue volatile)

13:54 <andrewrk> now I'll get those docs going

16:15 <diltsman> Is Zig inline assembly format the same as GCC inline assembly format?

16:15 <andrewrk> yes

16:15 <diltsman> At least that makes it easy to find documentation.

16:16 <diltsman> I will have to look at the ways to implement memcpy on ARM. __aeabi_memcpy, __aeabi_memcpy4, aeabi_memcpy8.

18:25 <nbjoerg> they are essentially the same, just with extra alignment