00:41 <andrewrk> sounds like accessing the path from the COFF section is more reliable\

00:48 <MajorLag> what's the best file to look at for understanding how typeInfo is structured?

00:58 <andrewrk> MajorLag, look at zig-cache/builtin.zig

01:00 <MajorLag> oh cool, I don't have to read cpp

01:01 <andrewrk> MajorLag, https://ziglang.org/documentation/master/#Compile-Variables

01:01 <andrewrk> docs were out of date but I fixed them

02:42 <GitHub19> [zig] andrewrk pushed 1 new commit to master: https://git.io/vpSUT

02:42 <GitHub19> zig/master 277b9cf Andrew Kelley: fix comptime code modification of global const...

03:05 <GitHub162> [zig] andrewrk pushed 1 new commit to master: https://git.io/vpSU2

03:05 <GitHub162> zig/master 4277762 Andrew Kelley: fix windows build system...

05:58 <MajorLag> hmm.. unfortunately it seems like typeinfo has some issues. Haven't managed to get it to not segfault.

06:05 <MajorLag> Think I have it narrowed down.

16:36 <Skilfingr> Hello

16:37 <Skilfingr> Does there exist an opengl wrapper for zig? Like http://glad.dav1d.de/

16:47 <MajorLag> Skilfingr: I think someone mentioned writing a loader for OpenGL functions, but I don't recall who it was.

18:48 <andrewrk> Skilfingr, you can use a C library, e.g. epoxy

18:48 <andrewrk> here's an example: https://github.com/andrewrk/tetris

18:48 <andrewrk> a pure zig library would be neat, but does not exist yet as far as I'm aware

19:02 <Skilfingr> Thanks. How is the pointer-reform going? Should I wait for this to finish before playing with zig?

19:13 <andrewrk> Skilfingr, I think that's kind of the same question as, should you wait for 1.0.0 to play with zig

19:14 <andrewrk> my answer is: if you want to be more of an end user, wait until 1.0.0. If you're happy to be a beta user where you participate in the development process, then you should jump in and start using master branch

19:17 <Skilfingr> haha, thats true :)

19:27 <Skilfingr> What is your strategy for 1.0? Do you have a timeline or bulletlist of features? Or is it more like when its done its done?

19:39 <andrewrk> Skilfingr, if you look at the issues on github, they all have a milestone. any issue with a milestone <= 1.0.0 is blocking the release of 1.0.0

19:39 <andrewrk> (which is most issues)

19:40 <Skilfingr> ok

19:48 <andrewrk> I predict 1.0.0 in 2 years

20:54 <andrewrk> wow I just got @newStackCall working

21:37 <GitHub96> [zig] andrewrk pushed 1 new commit to master: https://git.io/vpSDo

21:37 <GitHub96> zig/master a6ae451 Andrew Kelley: add @newStackCall builtin function...