11:29 <Sahnvour> hi, has anyone else errors with newlines not being '\n' on compiler explorer ?

20:00 <vegecode> Hey everyone, can anyone tell me if there is a sscanf type function? I see parseUnsigned and such.

20:34 <vegecode> can anyone point me to a repo with tests on functions that take file pointers so I can model my function tests after that?

20:36 <euantor> Any way to get more visibility into what the compiler is doing when using `zig build test`? I'm getting the following message when trying to test my project https://github.com/euantorano/resp3.zig: https://www.irccloud.com/pastebin/5RrBFFQJ/

20:36 <andrewrk> vegecode, I believe Jimmi (hejsil) has a proof-of-concept of a sscanf-like API

20:36 <andrewrk> probably in his "fun-with-zig" repo

20:37 <euantor> It only started failing to build when I added the functions dealing with `HashMap`s, so I guess I've broken something along the way there

20:37 <andrewrk> euantor, --verbose will list commands before executing them

20:37 <euantor> Awesome, will try that thanks

20:37 <andrewrk> but it should also print the last command that failed after it fails even without --verbose

20:38 <vegecode> Thanks.

20:39 <euantor> Damn, that didn't get me too much further. I did just notice I didn't finish implementing hash() full though, so I guess I'll fix that then try again. https://www.irccloud.com/pastebin/sU8CDtrn/

20:39 <andrewrk> euantor, it looks like zig, the compiler, is crashing, which is a bug in zig

20:40 <andrewrk> you can run the command again and see what it says: /usr/local/bin/zig/zig test /app/src/main.zig --output /app/zig-cache/test

20:40 <euantor> Ok, will try that then

20:42 <andrewrk> and then I'll give you the standard "you hit a compiler bug" instructions: 1. sorry about that, that's why we're still early beta 2. if you can reduce it down to a small test case, that's the best way to get it resolved, and for me to offer a workaround in the meantime

20:42 <euantor> Not a problem. I'll play some more and see wha I can figure out

20:58 <andrewrk> euantor, also if you're willing to use a debugger I can instruct you how to look at the backtrace and find out, in the source code, what caused the crash

21:01 <euantor> Great, thanks. I’m stepping away from the computer for an hour or so - might end up taking you up on that tomorrow

21:06 <vegecode> Could someone take a look and tell me why I'm getting this error?

21:06 <vegecode> https://pastebin.com/J3jd0rEv

21:06 <vegecode> I'll be back shortly

21:08 <andrewrk> we need a better error for this, but first of all your && isn't doing what you think it's doing

21:09 <andrewrk> actually that was the problem

21:09 <andrewrk> I'll open an error for this

21:13 <andrewrk> vegecode, https://github.com/ziglang/zig/issues/1877

21:16 <vegecode> Thanks