ChanServ changed the topic of #zig to: zig programming language | ziglang.org | be excellent to each other | channel logs: https://irclog.whitequark.org/zig/
Sahnvour has quit [Quit: Page closed]
davr0s has joined #zig
kristate has joined #zig
<kristate>
@andrewrk & everyone: I pinned ziglang to my github page and hope that everyone does the same: https://github.com/kristate
xtreak has joined #zig
Hejsil has joined #zig
xtreak has quit [Remote host closed the connection]
<kristate>
@Hejsil thanks for helping me out with CMakeLists.txt
<Hejsil>
Np :)
<kristate>
Hejsil: what do you think about the test skipping?
<GitHub98>
zig/master 99153ac Andrew Kelley: add std.math.big.Int.fitsInTwosComp...
davr0s has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
xtreak has quit [Remote host closed the connection]
xtreak has joined #zig
xtreak has quit [Client Quit]
wilsonk has quit [Read error: Connection reset by peer]
mahmudov has quit [Ping timeout: 276 seconds]
v1zix has joined #zig
v1zix has quit [Ping timeout: 252 seconds]
wilsonk has joined #zig
davr0s has joined #zig
v1zix has joined #zig
mahmudov has joined #zig
davr0s has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
<Bas_>
We don't have do while or anything, right?
<andrewrk>
Bas_, correct. while (true) { if (cond) break; }
<Bas_>
D=
<Bas_>
while(true) is generally horrible if you ask me. Though I can see it's sometimes unavoidable.
<andrewrk>
that's interesting that you say that, because I usually reach for while (true) before anything else
<andrewrk>
only sometimes does it end up being while (condition)
<Bas_>
really?
<DuClare>
I usually start with a while (1) but then find a nice way to express the condition outside the loop bodyu.
davr0s has joined #zig
<Bas_>
In my opinion it's often hard to see the control flow if there's breaks inside the loop.
<Bas_>
It depends a bit obviously. If there's not too much happening inside the loop it's fine.
v1zix has quit [Ping timeout: 252 seconds]
<DuClare>
That's why I (try to) move the condition to where it belongs. But it's not always obvious and I sometimes it's easier to work it out in the loop body first.
<DuClare>
It also depends on the complexity of the condition. If it gets complex, I don't cram it up there
<DuClare>
Multiple if statements in the loop body will be clearer than a big expression that tries to cover all the logic
Bas_ has quit [Ping timeout: 252 seconds]
hoppetosse has joined #zig
very-mediocre has quit [Quit: Page closed]
Bas_ has joined #zig
Bas_ has quit [Ping timeout: 252 seconds]
davr0s has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
davr0s has joined #zig
hoppetosse has quit [Ping timeout: 276 seconds]
davr0s has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
zolk3ri has quit [Remote host closed the connection]
redj has quit [Ping timeout: 268 seconds]
redj has joined #zig
davr0s has joined #zig
hoppetosse has joined #zig
davr0s has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
davr0s has joined #zig
davr0s has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]