examples: add pub_bytes

This was the point that I realized there's no reason to have the string
variants of the publishing methods. But also there's not really much
point in porting the other getting-started examples, since we've
covered all their functionality in the existing examples
(actually, this one is redundant too, but I have already done it, so
it's getting grandfathered in).

Porting some of the more interesting examples might be a good idea, but
those have a weird argument parser that I don't really want to port
(even though it is very simple in the way that it works). For the most
part, I think writing unit tests will do a better of flexing the
bindings.
This commit is contained in:
torque 2023-08-23 22:35:15 -07:00
parent af788a0536
commit 2e06f44aa8
Signed by: torque
SSH Key Fingerprint: SHA256:nCrXefBNo6EbjNSQhv0nXmEg/VuNq3sMF5b8zETw3Tk
2 changed files with 11 additions and 0 deletions

View File

@ -54,6 +54,7 @@ const Example = struct {
const examples = [_]Example{ const examples = [_]Example{
.{ .name = "request_reply", .file = "examples/request_reply.zig" }, .{ .name = "request_reply", .file = "examples/request_reply.zig" },
.{ .name = "headers", .file = "examples/headers.zig" }, .{ .name = "headers", .file = "examples/headers.zig" },
.{ .name = "pub_bytes", .file = "examples/pub_bytes.zig" },
}; };
pub fn add_examples(b: *std.build, options: ExampleOptions) void { pub fn add_examples(b: *std.build, options: ExampleOptions) void {

10
examples/pub_bytes.zig Normal file
View File

@ -0,0 +1,10 @@
const std = @import("std");
const nats = @import("nats");
pub fn main() !void {
const connection = try nats.Connection.connectTo(nats.default_server_url);
defer connection.destroy();
const data = [_]u8{ 104, 101, 108, 108, 111, 33 };
try connection.publish("subject", &data);
}