File Watching Implemented for kqueue

andrewrk · October 30, 2024, 5:29am

https://ziglang.org/devlog/2024/#2024-10-29

ktz_alias · October 30, 2024, 6:47am

I’d like to use this file-watch feature as API from the application program but not build.zig.
Do you have a plan?

andrewrk · October 30, 2024, 7:01am

github.com/ziglang/zig

Implement a server in the compiler that serves information about the compilation

opened 02:43PM - 16 Nov 17 UTC

andrewrk

enhancement proposal accepted frontend zig build system

This will not be [LSP](https://langserver.org), but a custom protocol just for Z…ig. A third party project can act as a proxy between this and LSP for that use case. This issue covers both the compiler process (e.g. `zig build-exe --listen=-`) acting as a server, as well as a meta-protocol exposed by the build system (i.e. `zig build --listen=-`). The latter will act as a multiplexer for the former. Once the initial implementation of both of these is created, follow-up issues can be made for specific features.

andrewrk · October 30, 2024, 5:05pm

I realize now you were talking about wanting to use OS file system watching features with the standard library, so my answer did not make sense. Sorry about that.

I think that it is difficult to provide an abstraction for file system watching without some kind of async API. Without it, there are too many variables to account for and platform differences, to the point that I think an application is better off writing their own application-specific abstraction, as you can see is done in the build runner.

So, I will revisit this when async’s fate is determined.

Judsen · October 30, 2024, 6:21pm

await fate()