03:29 <tiehuis> in the process of revisting a big number library, should be finished in a week or so

06:26 <alpha1220> Does zig support multi-methods? Or is there any example of visitor pattern in zig? I was planning to do `Crafting Interpreters` in zig.

06:39 <alpha1220> Also, are there macos master builds available for download? The download page lists only homebrew which I believe is the stable build?

10:24 <Hejsil> alpha1220, no multi methods. Dispatching based on types in Zig is explicit: https://github.com/zig-lang/zig/blob/0ba85ea6ff910c7a49ae036625b945c475c0f58c/std/zig/ast.zig#L65

10:25 <Hejsil> Though, you can do some tricks to make it less verbose: https://github.com/zig-lang/zig/blob/d7b029995c8ac678598de39aa106076dca232902/std/zig/ast.zig#L88

10:36 <alpha1220> Hejsil: Thank you.

12:31 <alpha1220> Can zig compile to android? If yes, how? I tried `--target-environ android --target-arch armv7`. Then adb'ed the binary to the device. And I get a segmentation fault.

13:55 <alexnask> $1 = {items = 0x2363000 "armebv8m_mainline", {heap_data = {length = 7021767589229589587, capacity = 792633534417233251}, bytes = "StackTrace\000\000\000\000\000\v"}, static LastByte = 15, static SmallBufferMaxItems = 15}

13:55 <alexnask> >.>

15:13 <perfwill> hey

15:27 <alexnask> hi

16:47 <perfwill> how am I supposed to do ref count in zig?

16:48 <perfwill> like an ArrayList that automatically gets deallocated when it goes out of scope

16:54 <alexnask> There is currently no RAII capability

16:55 <alexnask> I think there are proposals for some simple form

16:55 <alexnask> What people usually do is: var resource = get_resource(); defer free_resource(resource); // Do stuff with resource...

17:09 <perfwill> got it

17:09 <perfwill> But how are we supposed to structure allocators in zig?

17:09 <perfwill> I see it being required everywhere

17:11 <perfwill> should we pass it down to functions or should we put it in a common import or something?

17:31 <alexnask_> Perfwill, in your own code thats your decision to make

17:31 <alexnask_> Personally i take it as a func argument

17:31 <alexnask_> And store it in structs that own mem on the heap

17:32 <alexnask_> A global is ok but i like making it explicit what can allocate and what cannot

17:34 <alexnask_> Plus it makes it easier to switch parts of the code tp use another allocator if you want to test it out