ChanServ changed the topic of #zig to: zig programming language | ziglang.org | be excellent to each other | channel logs: https://irclog.whitequark.org/zig/
qazo has joined #zig
qazo has quit [Ping timeout: 240 seconds]
reductum has joined #zig
qazo has joined #zig
qazo has quit [Ping timeout: 240 seconds]
qazo has joined #zig
qazo has quit [Read error: Connection reset by peer]
reductum has quit [Quit: WeeChat 2.2]
dpk has quit [Ping timeout: 260 seconds]
dpk has joined #zig
davr0s has joined #zig
davr0s has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
davr0s has joined #zig
bheads has joined #zig
wilsonk has quit [Read error: Connection reset by peer]
fsateler has quit [Read error: Connection reset by peer]
fsateler has joined #zig
aiwakura has quit [Quit: Ping timeout (120 seconds)]
aiwakura has joined #zig
very-mediocre has joined #zig
unique_id has joined #zig
<unique_id>
Since no one has said anything in 24hours+ according to the log: Currently working on reliable in-order messaging over UDP for gamedev. Thought I'd give it a go myself to learn how it works rather than relying on a blackbox I didn't understand.
<unique_id>
Zig is really nice for this
davr0s has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
davr0s has joined #zig
<bheads>
Sounds fun, I put zig on hold until the syntax issues have been resolved. I have one project that needs to be updated already
<ltr_>
some kind kind of related, i was reading about udp protocols, and revisiting UDT, i found it an amazing protocol, it uses my bandwidth at full from anywhere
<bodie_>
unique_id, that sounds like a blast. is your source open?
<bodie_>
s/open/public/
<bheads>
Whats your plan for dealing with lost messages?
<unique_id>
bodie_: I haven't open sourced anything at the moment. bheads: I simply haven't updated to that commit since I found it extremely likely that the syntax change would be altered.
<unique_id>
bheads: I'm figuring that out at the moment. What I know is that each packet has a sequence number and lost packets are not sent with the same sequence number. Sequence numbers just keep incrementing until they wrap around. This way acking can be a single sequence number + a bit field of the 32 previous sequence numbers. So you duplicate acks like crazy but in an incredibly compact way. I'm learning this from Glenn Fiedler's
<unique_id>
articles. Reliability is built on top of this
<unique_id>
So each bit indicates whether a package has been received, for something like 32 total packets.
<unique_id>
packet*
<unique_id>
I'm never good at explaining things, simple or not :)
davr0s has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
darithorn has joined #zig
davr0s has joined #zig
wilsonk has joined #zig
porky11 has joined #zig
SimonNa has joined #zig
unique_id has left #zig ["Konversation terminated!"]
clownpriest has joined #zig
Ichorio has joined #zig
clownpriest has quit [Ping timeout: 264 seconds]
clownpriest has joined #zig
<MajorLag>
andrewrk, or anyone else who knows: I want to see how zig will pack a struct on a big-endian arch. Whats the best way to do that considering there are no big-endian archs or OSs supported by std? I've tried to emit asm for MIPS but it doesn't seem to be doing anything.