ChanServ changed the topic of #zig to: zig programming language | ziglang.org | be excellent to each other | channel logs: https://irclog.whitequark.org/zig/
jfo1 has joined #zig
jfo has quit [Ping timeout: 255 seconds]
hasen_judy has quit [Remote host closed the connection]
hasen_judy has joined #zig
hasen_judy has quit [Remote host closed the connection]
jfo1 has quit [Ping timeout: 256 seconds]
hopppetosse has quit [Ping timeout: 276 seconds]
jfo1 has joined #zig
jfo1 has quit [Ping timeout: 252 seconds]
dd3 has quit [Ping timeout: 256 seconds]
jfo1 has joined #zig
zesterer has quit [Quit: zesterer]
jfo1 has quit [Ping timeout: 260 seconds]
jfo1 has joined #zig
jfo1 has quit [Ping timeout: 255 seconds]
jfo1 has joined #zig
jfo1 has quit [Ping timeout: 240 seconds]
jfo1 has joined #zig
jfo1 has quit [Ping timeout: 276 seconds]
jfo1 has joined #zig
<SimonNa>
jfo1: thanks for the quick fix for 'zig build', I already tried it :)
jfo1 has quit [Ping timeout: 256 seconds]
jfo1 has joined #zig
jfo1 has quit [Ping timeout: 265 seconds]
jfo1 has joined #zig
jfo1 has quit [Ping timeout: 255 seconds]
jfo1 has joined #zig
jfo1 has quit [Ping timeout: 276 seconds]
jfo1 has joined #zig
jfo1 has quit [Ping timeout: 252 seconds]
jfo1 has joined #zig
jfo1 has quit [Ping timeout: 256 seconds]
hasen_judy has joined #zig
hasen_judy has quit [Ping timeout: 265 seconds]
jfo1 has joined #zig
jfo1 has quit [Ping timeout: 256 seconds]
jfo1 has joined #zig
jfo1 has quit [Ping timeout: 255 seconds]
davr0s has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
tridactyla has quit [Remote host closed the connection]
tridactyla has joined #zig
dd3 has joined #zig
hopppetosse has quit [Ping timeout: 260 seconds]
hasen_judy has joined #zig
hasen_judy has quit [Ping timeout: 240 seconds]
hopppetosse has joined #zig
<MajorLag_>
Attempting to do things of dubious utility is a good way to surface compiler bugs, I'm finding.
<andrewrk>
yeah. we'll get those edge cases ironed out eventually, but it makes more sense to focus on bigger picture issues while things are unstable
<MajorLag_>
wait, so returning var is something you want to allow? How would that work? What if the function chooses a different type to return depending on runtime conditions?
<MajorLag_>
I suppose you just don't allow that. That'd make sense.
<andrewrk>
MajorLag_, then it gets resolved the same way if your switch prongs have different types, or if an if-else statement body and else have different types
<MajorLag_>
If I understand correctly, that means which type is being acted on has to be determinable at compile time, correct?
<andrewrk>
yes
<andrewrk>
but you can, for example, return null from one place and i32 from another place, and this gets resolved as ?i32
<andrewrk>
in the compiler code we call this "peer type resolution"
Hejsil has quit [Read error: Connection reset by peer]