ChanServ changed the topic of #zig to: zig programming language | ziglang.org | be excellent to each other | channel logs: https://irclog.whitequark.org/zig/
<andrewrk>
stratact: what kind of checking?
<andrewrk>
I'm about to lose internet connectivity for about 6 hours. Back later
<stratact>
I mean the reference checking
MajorLag1 has quit [Ping timeout: 276 seconds]
MajorLag1 has joined #zig
commander has quit [Remote host closed the connection]
MajorLag1 has quit [Ping timeout: 255 seconds]
MajorLag1 has joined #zig
davr0s has joined #zig
MajorLag1 has quit [Ping timeout: 276 seconds]
MajorLag2 has joined #zig
MajorLag2 has quit [Ping timeout: 276 seconds]
MajorLag1 has joined #zig
quc has quit [Ping timeout: 256 seconds]
<MajorLag1>
stratact, what precisely would separate zig from rust then?
<stratact>
MajorLag1: well, it would be a language with a different syntax for different approaches to programming and thinking. Also the same could be said for what would separate zig from C if zig is not safe to begin with.
<stratact>
I just think it's really crucial to have safety in this day and age.
<MajorLag1>
quite a lot actually. C is very lose with its casting, has lots of undefined behavior, and the mess that are macros. Zig's saftey comes from built in debug checks, explicit syntax, better error checking, etc.
<MajorLag1>
It rather like that it doesn't force a memory management paradigm on programers like rust does.
<stratact>
I guess that's an approach I haven't thought of. So how does debug checking work?
<MajorLag1>
The compiler does a lot of static checks, and then in debug mode (which is the default for builds) the compiler inserts a lot of checks for things like out-of-bounds array access, integer overflows, pointer alignment, etc. So a lot of bugs are caught in testing. Then you can compile a release-fast or release-small version without all the extra checks. Or you can compile release-safe and keep the checks but not the
<MajorLag1>
even turn checking on and off at the scope level with @setRuntimeSafety.
zolk3ri has quit [Remote host closed the connection]
zolk3ri has joined #zig
<MajorLag1>
There's some more runtime checking we'd like to do around pointers and resource handling, so in that way zig is planning to add more safety: https://github.com/ziglang/zig/issues/782 for instance.
zolk3ri has quit [Client Quit]
zolk3ri has joined #zig
davr0s has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
<stratact>
MajorLag1: gotcha, thanks for sharing
zolk3ri has joined #zig
zolk3ri has quit [Quit: leaving]
dbandstra has joined #zig
<dbandstra>
andrewrk: i think while docs should mention the `while (a) |b| : (c)` syntax (noticed this in std somewhere, but it's not documented)
<dbandstra>
about the windows sdk thing, is the "Windows Kits" folder something installed by visual studio? if so then whatever, it's no big problem for me. i'm just booted into windows for other reasons and was hoping i could play with zig at the same time
<MajorLag1>
IIRC Windows Kits is put down by the SDK install.
<dbandstra>
SDK being...
<MajorLag1>
like, the Windows 10 SDK
<dbandstra>
sorry most of my knowledge of windows programming dates to like visual c++ 6
<dbandstra>
i have the reg key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Kits\Installed Roots\KitsRoot81 = C:\Program Files (x86)\Windows Kits\8.1\
<dbandstra>
and i have this folder: C:\Program Files (x86)\Windows Kits\8.1\Lib\winv6.3 (contains a subfolder called "um")
<dbandstra>
so i don't see how os_find_windows_sdk is not succeeding
<MajorLag1>
yeah, that seems like it should work...
xtreak has joined #zig
xtreak has quit [Remote host closed the connection]
fjvallarino has quit [Remote host closed the connection]