ChanServ changed the topic of #zig to: zig programming language | ziglang.org | be excellent to each other | channel logs: https://irclog.whitequark.org/zig/
return0e has quit [Ping timeout: 252 seconds]
return0e has joined #zig
redj has joined #zig
bodie_ has quit [*.net *.split]
moxotter has quit [*.net *.split]
meena has quit [*.net *.split]
Guest73197 has joined #zig
meena has joined #zig
nodist has joined #zig
nodist has quit [Client Quit]
utzig has quit [*.net *.split]
tyler569 has quit [Ping timeout: 260 seconds]
return0e has quit [Remote host closed the connection]
tyler569 has joined #zig
mnoronha has joined #zig
return0e has joined #zig
<scientes>
andrewrk, you on? you want to set up the github hook for arm64 CI?
<dimenus>
indeed, I see you made the leap to working on Zig fulltime-ish
<andrewrk>
it is full fulltime, and I'm loving it
<andrewrk>
DutchGh0st, you can call cancel anytime, and but the cancellation happens at the next suspend point
<andrewrk>
a suspend point is: suspend, await, or return
<DutchGh0st>
Oh hehe, but thats about multithreaded coroutines, I think I need to do some single threaded coro's first to get a better idea of how it all works
<andrewrk>
with a single thread, if you use cancel, then the thing you're cancelling must be at a suspend point
<andrewrk>
I mean, it will, because that's the only way the single thread could be at the cancel instruction and not in the coroutine
<DutchGh0st>
teagg U see
<DutchGh0st>
wow, cant even type
<DutchGh0st>
*yeahh I see
<andrewrk>
dimenus, I'm working on windows stack traces
<dimenus>
nice, looks like LLVM 6 made some improvements in that area as well
kristate has joined #zig
kristate has quit [Ping timeout: 240 seconds]
<andrewrk>
I don't suppose anyone in here knows how to unwind a windows stack?
<andrewrk>
it appears to be different than on macos and linux
<unique_id>
andrewrk, I should tell you... since I've had a foolish resurgance in interest in my own language I played around with nvim + the language server protocol recently. It's turns out that it's a really pleasurable protocol. It took no time to set it up. They've even done some outside of the box thinking (at least I haven't heard of this before) where the language/server can report locations of Color, so the IDE can display a small
<unique_id>
colored box next to RGB values, or allow a color selection box for an alternative input method.
<unique_id>
This idea can of course be taken much further :)
<andrewrk>
neat - I think we're only a few months away from language server protocol in stage2
<unique_id>
sounds good
mnoronha has joined #zig
mnoronha has quit [Ping timeout: 246 seconds]
kristate has joined #zig
kristate has quit [Ping timeout: 250 seconds]
kristate has joined #zig
kristate has quit [Ping timeout: 240 seconds]
mnoronha has joined #zig
MajorLag has quit [Ping timeout: 244 seconds]
MajorLag has joined #zig
mnoronha has quit [Ping timeout: 240 seconds]
kristate has joined #zig
kristate has quit [Ping timeout: 240 seconds]
dimenus has quit [Quit: Leaving]
kristate has joined #zig
kristate has quit [Ping timeout: 240 seconds]
mnoronha has joined #zig
mnoronha has quit [Ping timeout: 252 seconds]
noonien has quit [Quit: Connection closed for inactivity]
davr0s has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]