Techatrix

Mason's [package.yaml](https://github.com/mason-org/mason-registry/blob/c4726899a13591ac1d07ff8f2199db7187d90147/packages/zls/package.yaml#L86-L87) for ZLS uses vscode-zig's `package.json` to provide information about config options. This should not be done because vscode-zig options don't exactly match what ZLS uses. I will look...

> Can confirm that setting semantic tokens to "partial" does fix the issue, but at the same time highlighting changes in places where I prefer it would not This should...

This could be related to #1537

The provided logs are a bit hard to read but based on what I can decipher, the first error that occurred is the following: ``` failed to process notification-textDocument/didChange: error.InvalidParams...

> Does the tarball include hard-links, unicode, path/filenames? no > Can you provide an example tarball? Did you overlook the "Example with PowerShell" or "Example with NodeJS" (collapsible) section? They...

> There are a couple of problems with your first example: After switching to `Start-Process -FilePath "$Tar" -ArgumentList "-tvvf -" -RedirectStandardInput 7z.zip -Wait -NoNewWindow` instead of `Get-Content` that problem goes...

The inlay hint now displays `struct{ *const [1:0]u8, *const [2:0]u8 }`.

In case you missed them, these [comments](https://github.com/zigtools/zls/pull/2331#pullrequestreview-2876877037) have not been addressed yet.

The pinned Zig version has been removed from `ziglang.org/builds/`. Updating the nix flakes will update the Zig version. fixed by da79fcb512a5f28b7de9ea9a15b8188d0f3d2a43

> @Techatrix, I'm hoping we'd be able to collaborate on integrating this with ZLS? Definitely. I'd be happy to help wherever I can to get the compiler protocol (or whatever...