00:00 <marijnfs> valgrind still complains a lot though, there might be more such issues

00:14 <marijnfs> nvm seems just valgrind freaking out about vulkan

01:34 <marler8997_> I just build LLVM without the -DCMAKE_PREFX_PATH option... I think it's only necessary for clang/zig but not for LLVM. I'll remove it from the wiki so long as no one has any objections?

01:34 <marler8997_> from this wiki: https://github.com/ziglang/zig/wiki/How-to-build-LLVM,-libclang,-and-liblld-from-source#posix

01:38 <mikdusan> marler8997_: you probably have llvm-config in your default path. but not all OS (like macOS) have that and need a way to locate LLVM

01:39 <marler8997_> you need to locate llvm when you're building llvm?

01:40 <mikdusan> ah sorry nvm, i see what you mean now

01:43 <andrewrk> marler8997_, please just leave it in - it's simpler to pass the argument for everything that is part of this "local root" path

01:44 <andrewrk> for example sometimes there is another dependency: https://github.com/ziglang/zig/wiki/Building-Static-Zig-on-macOS

01:44 <marler8997_> oh I already removed it. I removed as it was confusing for me. I was trying to figure out what libraries LLVM was looking for

01:44 <marler8997_> of course I can un-remove it

01:44 <marler8997_> but it still confuses me

01:45 <marler8997_> oh...so it could depend on zlib?

01:45 <andrewrk> think of it like this: we're creating a directory that is the prefix for everything we're about to build from source

01:46 <marler8997_> k, I'll revert my change

01:46 <andrewrk> you are correct that technically the first dependency doesn't need the parameter

02:41 <marler8997_> found a way to loop through varargs

02:44 <marler8997_> I made a function that given a comptime_int, returns an array of comptime_int where each entry is it's own index

02:44 <marler8997_> then I just do an inline for loop through that "index array" of comptime_int

03:31 <marler8997_> my solution could use some improvement though

03:31 <marler8997_> here's the challenge, can you implemet this function? pub fn allocVarargs(comptime T: type, allocator: *std.mem.Allocator, args: ...) ![]T;

03:31 <marler8997_> I've got a solution but want to see if anyone has a better one

03:36 <marler8997_> the function allocVarargs returns an array of the given variadic args

03:57 <mikdusan> marler8997_: here's my naive solution: https://gist.github.com/mikdusan/8377573c5a1659f975d6a86cbaae0fa2

03:58 <marler8997_> shoot that works

04:00 <marler8997_> I couldn't figure out how to loop through a comptime index, thanks for this, it helps alot

04:01 <marler8997_> Here's my final solution:

04:01 <marler8997_> https://gist.github.com/marler8997/21be72451adea88560b0b13c67de0e86

04:01 <marler8997_> thanks again for your help

04:01 <mikdusan> no problemo

04:01 <marler8997_> maybe this is a candidate for inclusion in the standard library?

04:01 <mikdusan> varargs is changing. so i don't know re: std library

04:02 <marler8997_> yeah I figured, I was thinking that in any case this functionality would still be supported though

04:02 <marler8997_> but I don't know for sure since I don't know where it's going

04:02 <marler8997_> but I would think having a function to convert varags to an array would still be supported no matter what

04:03 <marler8997_> I'll make a PR so it can be discussed

04:06 <mikdusan> maybe scan over https://github.com/ziglang/zig/issues/208 ; notably Andrew's comment: https://github.com/ziglang/zig/issues/208#issuecomment-440504195

04:07 <marler8997_> remove varargs meaning no more varargs?

04:07 <mikdusan> take with grain of salt i might have this understanding wrong but:

04:08 <mikdusan> `allocVarargs([]const u8, arena, "one", "two", "three")`

04:09 <marler8997_> it looks like the current plan is to remove varargs based on what I'm reading

04:09 <mikdusan> would become `allocVarargs([]const u8, arena, .{"one", "two", "three"})`

04:09 <marler8997_> the syntax looks weird though

04:09 <marler8997_> instead of warn("hello {} you are {} years old", name, args)

04:10 <marler8997_> it would be warn("hello {} you are {} years old", .{name, arg})

04:10 <mikdusan> yes that is my understanding

04:10 <marler8997_> but maybe it would look fine with some "getting use to"

04:11 <marler8997_> well thanks for the info, since the plan is to remove varargs I won't push a PR

04:11 <marler8997_> I see one advantage is it allows multiple varargs

04:11 <marler8997_> that's pretty cool

04:12 <marler8997_> at first glance it looks like a nice alternative to tuples

04:18 <marler8997_> I andrew say "No Tuples". I'm looking for the information on why that decision was made. I would love to see a place where we could see decisions made in the language and the reasons for them.

05:34 <daurnimator> marler8997_: I'm not sure where it is on the issue tracker. but varargs can't be removed: they're part of the C ABI and hence required for interoperation with C.

05:38 <marler8997_> oh sure, I'm talking about zig's varargs

05:38 <emekankurumeh[m]> is there a way to force zig to output debug gdb-friendly debug info on windows?

05:39 <marler8997_> zig's varargs (currently used with the format function) is more like a tuple

05:40 <marler8997_> I just finished converting my first project to zig. Fun stuff: https://github.com/bettertools/git-extra

06:35 <gonz_> c, d & zig :D

06:35 <marler8997_> Never finished the C version :)

08:38 <gonz_> I really like D conceptually, but I feel like it's so big. How I ended up looking at zig was actually that I was looking at using D as a better C, but I feel like I found something that fit that much better out of the box.

08:39 <gonz_> Though, to be fair, I have no practical experience with D.

13:48 <tralamazza> any idea why this crashes the compiler? https://zig.godbolt.org/z/ACOnoy

13:48 <tralamazza> trunk only, 0.4 works

13:59 <marler8997_> gonz_: I've written hundreds of thousands of lines of D code at this point. It's got some really cool features but also has a fair amount of issues. I've written my own standard library in D to combat some of those issues https://github.com/marler8997/mar but there are also issues in the language. It's also very static now, any changes to the language must go through a multi-year proposal process, a process which is broken (I've

13:59 <marler8997_> had one that's about 3 years old and still going). The creator Walter is pretty set in his ways, he's very poor at maintaining a positive community and almost impossible to discuss language ideas with. He knows alot, but seems to only value features in the language that help his style of programming, which is very archaic. Zig has some really cool ideas that solve alot of the issues D has. It's currently not as "nice" to read and

13:59 <marler8997_> is missing some features, but the core of the language seems to be going in the right direction, and it's still young enough to make breaking changes and move in a new direction if it's deemed a better one (i.e. varargs vs tuples vs anonymous structs). I have alot more to say on the subject but I have to go for now. I was thinking of making a post about my experience porting a couple of my projects from D to Zig and explaining what

13:59 <marler8997_> I think the differences are.

15:06 <gamester> marler8997_: Wow a heavy D user, nice! Many eons ago I was writing an application that needed to load and unload DLLs at runtime. I considered D but it had no ability to handle this simple task, at least without leaking memory. It struck me as a really weird thing to not have figured out for a language that seemed back then to be focused on systems programming. I've never grokked what D is trying to be.

15:12 <gamester> marler8997_: Now that C#/.NET is becoming open source, does that place C# as a competitor to D?

16:02 <scientes> gamester, C# is a virtual machine, while D is compiled to native code. they are totally different

16:02 <gamester> I disagree

16:05 <scientes> If Java a competitor to C++?

16:06 <gamester> D != C++

16:06 <gamester> D is a GC language

16:06 <gamester> with ability to sidestep it

16:06 <scientes> oh yes I forgot about that "better-C" doesn't have a gc however

16:06 <scientes> that was the part I was interested in

16:13 <gamester> There's also .NET Native now which precompiles your code to native code, statically links in the required portions of the .NET framework, and does global analysis on all of this. I don't know if you get an exe or something more like a dll.

16:14 <marijnfs> is there a reason why insertionSort is in an extra block?

16:27 <scientes> i think the other sort uses it

16:31 <marijnfs> I implemented a binarySort and it seems faster

16:40 <andrewrk> gonz_, hey thanks for the support

16:44 <andrewrk> I ran into a snag yesterday in the result location branch. went to bed frustrated but woke up with a solution

17:31 <tralamazza> hi andrewrk, I'm trying my hand at zig for embedded. I'm trying to avoid asm, while doing the startup code I think I stepped into a compiler bug (or at least crash) https://zig.godbolt.org/z/ACOnoy

17:59 <scientes> here is the backtrace to that http://paste.debian.net/1088093/

18:00 <scientes> tralamazza, you should probably report a bug so this can be tracked

18:00 <scientes> if the compiler crashes it is ALWAYS a bug

18:09 <tralamazza> I want a struct for my vector table (instead of an array), i thought of using the @typeInfo to do the @export weak at compile

18:09 <tralamazza> basically how i got to the bug

18:12 <scientes> tralamazza, https://github.com/ziglang/zig/pull/2694

18:13 <scientes> actually he probably won't want to merge that based on the assert()

18:14 <tralamazza> ty scientes

18:14 <tralamazza> but it seems to be a regression, since 0.4 does not crash

18:15 <andrewrk> tralamazza, fixed in master

18:16 <andrewrk> I mean, I just pushed a commit

18:19 <tralamazza> neat ty

22:39 <tralamazza> I'm trying to set the target in my build.zig, a bit confused how to set the subarch. I want something like exe.setTarget(builtin.Arch.thumb.v7m ...

22:41 <curtisf> What's the best way to format a chain of method calls in Zig? zig fmt puts them all on the same line which is hard to read. I can put a `//` at the end of each line but that's a bit weird

23:41 <gamester> curtisf: you can put a comma after the last argument like so: func(arg,)

23:49 <curtisf> There aren't arguments here, I'm trying a "fluent" style: https://hastebin.com/ewizigeveq.zig

23:52 <curtisf> I think I'm more or less happy with how it looks though, since I'm being explicit where I want my breaks