05:30 <Summertime> so there is a while loop that can handle null output, and one that can handle error output, but there isn't a way to easily handle output which can be nullable and can throw an error?

05:37 <andrewrk> Summertime, correct - not at the same time

05:38 <andrewrk> if and while support the same syntax with regards to optionals and error unions

05:38 <andrewrk> so you will probably have an outer while loop and an inner if

06:12 <Summertime> https://github.com/Summertime/posix-implementations/blob/master/pozig/src/echo.zig how's my driving? (other than me using a woefully out of date version)

06:17 <Summertime> one thing that's kinda eating at me, is I've got multiple calls to stdout.write which can error, in slightly different scopes, `try` will push it up scopes, but how do I handle it before it hits main?

06:18 <andrewrk> Summertime, is this posix-only code? you might want to use args.nextPosix() instead of args.next()

06:18 <andrewrk> the posix only API does not require an allocator and cannot fail

06:20 <andrewrk> have a look at using `if` and `catch` with errors

06:28 <Summertime> m, still not quite putting it together mentally, like, I know I can catch on each write, I know I can use if to conditionally run code if its an noterror/error, but I'm not too sure what is the zigish? approach with this code, in other languages it'd be a trycatch, in zig, do I wrap the code in a function instead?

06:29 <Summertime> I think I could just really muck around with the panic handler and call it a day, but that seems a bit hackish

06:30 <andrewrk> are you looking to avoid `try` in main? if so why?

06:30 <andrewrk> or rather, a better question - what are you trying to accomplish?

06:32 <Summertime> if there is an error writing to stdout, I want at most the application to give an non-zero exit, and have zero output on stderr

06:34 <Summertime> I don't mind try in main, but I just want it to say and act exactly how I want if an error happens... I guess panic handler is the answer then?

06:35 <Summertime> oh, panic handler doesn't go if errors are returned from main?

06:36 <andrewrk> Summertime, that will happen in a release-fast build

06:36 <andrewrk> in release-fast returning an error from main just does exit(1)

06:37 <andrewrk> https://github.com/ziglang/zig/blob/dc2dfef0a22dba646c87fd94ff421fa85fd79493/std/special/bootstrap.zig#L101-L112

06:37 <andrewrk> ok my mistake - actually in release-fast mode it prints error: Foo

06:38 <andrewrk> if you want it to print nothing and do exit(1), I don't think you need to mess with the panic handler. I think you just want to have main do: main2() catch |err| exit(1)

06:39 <andrewrk> or, make the return value of main u8, and then `main2() catch return 1`

06:42 <Summertime> easy enough, thanks for the guidance!

06:43 <Summertime> https://github.com/ziglang/zig/issues/1048 I guess anonymous functions would probably make such a pattern easier too

10:03 <presiden> is there similar function like warn, but for stdout?

10:03 <presiden> something similar to printf?

13:01 <Hejsil> presiden, https://gist.github.com/Hejsil/141d1433a64a3495636453860cee3abd

13:20 <presiden> Hejsil: owh, I see

13:20 <presiden> Is the std documentation out there somewhere?

13:21 <Hejsil> Not yet: https://github.com/ziglang/zig/issues/21

13:27 <presiden> I see

15:11 <andrewrk> MajorLag, have a look at https://ziglang.org/download/

15:11 <andrewrk> the master branch stuff is auto-updated now

17:39 <wilsonk> @andrewrk Thanks for the dark theme for the ziglang documentation!!! :). SOOOO much more readable and easy on the eyes!

17:53 <andrewrk> wilsonk, you're welcome

18:31 <Jenz> I want to read the contents of a file into a var. In github:ziglang/zig/examples/cat the program uses a buffer, [1024 * 5]u8, but how do I do it if I want variable length?

18:32 <andrewrk> Jenz, perhaps do you want std.io.readFileAlloc?

18:33 <andrewrk> this API is missing a parameter to set a maximum allowed file size - so be sure to use it only if the length of the file is not user input.

18:33 <Jenz> Thanks a ton andrewrk!