06:29 <ammen99> ifreund, asking since I am teying to figure out whether to release wayfire for wlroots 0.12 or to wait for 0.13 if you'll be ready soon

06:30 <ammen99> (and btw thanks for the answer ;))

09:12 <edrex> ifreund: thanks. I haven't done a ton of C programming so I didn't remember the last two _PATHs needed exactly..

09:12 <edrex> i'

09:14 <edrex> m making a concerted effort to get comfortable with working with lower-level tools lately. Just tired of tiny programs having massive binaries, slow startup times, super long dep lists etc.

09:18 <edrex> I'm feeling very curious about Zig. I'm thinking of trying it out for a console menu tree tool I am about to start work on.

09:20 <edrex> Basically a tool for creating a tree of nested binding modes, sort of a keyboard driven start menu thingie.

09:20 <edrex> (console will be first backend, then maybe cairo)

09:22 <edrex> hey also, I started using Kakoune as my daily editor a week or so ago. I think it's going to stick!

09:22 <edrex> I tried it before but i think you mentioned it in channel and I ended up picking it back up

09:35 <ifreund> ammen99: oh is wlroots 0.13 blocked only on me? I thought emersion had some regressions to track down first or something

09:36 <ifreund> I'm very busy with real life this week but could probably finish up what's left to do next week

09:37 <ifreund> edrex: very cool, Zig is a great language IMO though there will still be occasional breaking changes before 1.0 of course

09:39 <ifreund> comptime is a great solution to most of the problems I have with C, and more pointer types + optional types solve the rest

09:40 <ifreund> for your start menu thing, you could also just start the console version in a temporary, floating terminal instead of doing real graphics, I used fzf as my launcher like that for a while

09:41 <ifreund> and cool to hear that I've inspired more Kakoune usage!

09:41 <ifreund> what editor are you coming from?

09:44 <ammen99> ifreund: yeah I think we might want to wait until all regressions are fixed on nouveau+intel

09:44 <edrex> yeah, that's what I'm thinking to do. using foot now, and it comes up heckin' fast :)

09:44 <ammen99> I think I'll just stick to 0.12 this time and release 0.7.1 once 0.13 is out :)

09:45 <ifreund> cool :)

09:45 <ifreund> edrex: foot is super fast in client/server mode yeah :)

09:45 <edrex> i watched the Zig 1.0 talk and comptime seems really nice. Didn't learn about the Zig pointer types yet tho.

09:46 <edrex> oh, i'm not even running it that way (assuming it doesn't automatically daemonize or something)

09:47 <ifreund> basically instead of having one type for all pointers like in C, Zig has different types for pointer-to-one, pointer-to-many, sentinel-terminated-pointer, and slices (pointer + lenght)

09:47 <ifreund> yeah even without client-server mode foot has super fast startup

09:47 <edrex> yeah, i have a bunch of fzf (as well as dmenu/wofi) scripts that I want to unify under one toplevel menu.

09:49 <edrex> oh right, he did cover that in the talk. super cool. Slices are familiar from Go

09:51 <edrex> i'm also curious how the async story is, since I do a lot of things with concurrent IO in (theoretical, currently non-existent) $DAYJOB

09:52 <edrex> I have a highly plugged up vim. I was using spacemacs for a couple of years. I really like the way the leader key / user key menus work in spacemacs, and that is the UI inspiration for the menu thingie.

09:54 <ifreund> the language level async support in zig is very low-level and manual (and still pretty experimental currently). Basically it just allows you to suspend and resume functions, storing the function's stack frame wherever you like

09:55 <ifreund> any event loop/executor is implemented in user-land of the language, there's one in the std and several others developed by the community

09:55 <ifreund> this is a good intro if you're curious: https://ziglearn.org/chapter-5/

09:56 <edrex> cool, i will take a look when I do my menu thingie

10:34 <edrex> Does interacting with a C library from Zig generally require creating bindings? I'm looking at https://github.com/dankamongmen/notcurses/tree/master/src/lib

10:35 <edrex> sorry OT, i should go find a #zig room

10:37 <ifreund> edrex: it's just #zig

10:38 <edrex> :)

10:41 <ifreund> edrex: to answer your question though, zig can autogenerate bindings for you with `zig translate-c` on the header or `@cImport()`/`@cInclude()`

10:41 <ifreund> I only made manual bindings for libwayland/wlroots because there could be a signficant step up in type safety over the autogenerated versions

10:42 <ifreund> until a couple months ago river just used @cImport() for everything

10:44 <edrex> oh ok, thanks for explaining it to me. I was seeing wlroots-zig made me wonder.

13:46 <MrSnookums> Hello Im getting the following error when building river "./river/main.zig:71:50: error: no member named 'outStream' in struct 'std.fs.file.File"

13:47 <ifreund> MrSnookums: what zig version?

13:48 <ifreund> (river requires 0.7.1)

13:48 <MrSnookums> 0.8.0-dev.1026+d5b0a963d

13:48 <ifreund> that probably won't work

13:48 <MrSnookums> thank you, I will try to downgrade it