I don’t think the language is missing anything to do this. I think there are a few other ecosystems that have support for it.
I assume you mean the failing copy on completed builds when the code folder is a mounted NTFS filesystem. The easiest way to fix that is to make a symbolic link for the .zig-cache/ folder in your project to one properly inside Linux like ~/.zig-cache once you do that it builds just fine.
Good thinking, I’ll keep that up my sleeve.
Any missing examples or unclear docs, I wouldn’t consider these a strike against Zig unless the language had been 1.0 for a year or two and had made no effort to improve this.
I think real hurdle is validating the examples in the documentation itself.
I would wish for maintainers to sort through Pull Requests.
There are 100+ all checks passing PR, that just wont get merged.