DraagrenKirneh

Added a PR #15248 for the fields in package.zig.zon and Manifest.zig, but did create any validation logic yet since the command "zig pkg" do not seem to exist yet. Perhaps...

Maybe it is worth to change the ReadError in Client.zig to also include the more fine grained TLS errors instead of generalizing them to TlsFailure? It would help to pinpoint...

Here is a trace from a debug build for BadReaderState. ``` error: BadReaderState C:\Git\zigcode\zig\lib\std\compress\deflate\decompressor.zig:461:25: 0x7ff6b9903935 in read (zig.exe.obj) return self.err.?; ^ C:\Git\zigcode\zig\lib\std\compress\gzip.zig:128:23: 0x7ff6b990329f in read (zig.exe.obj) const r = try...

Looks like this is now fixed in latest master by: https://github.com/ziglang/zig/commit/ab37ab33ce94b4fb6536bcc2f3981c0cc257c9f0 With it package download works, If i revert it I get `BadReaderState` etc.

I managed to link the wrong commit... The correct one that fixes it is https://github.com/ziglang/zig/commit/ab37ab33ce94b4fb6536bcc2f3981c0cc257c9f0 cc: @renerocksai

I think the service definition can be written even clearer: ``` service = "service" serviceName "{" { option | rpc | emptyStatement } "}" rpc = "rpc" rpcName streamType "returns"...