nats.zig

factotum/nats.zig

Fork 0

Commit Graph

Author	SHA1	Message	Date
torque	65ab46f714	connection: eliminate String method variants After contemplating this for a little bit, there's no point in exposing these separately from the plain variants. Even nats.c internally calls its plain variants after calling `strlen` on the input. Zig benefits from having nicer pointer types than C, so we get "string" handling for free from the fact that the standard variants take slices anyway.	2023-08-23 22:27:33 -07:00
torque	18205a5533	examples: add statistics to request_reply I should probably write some tests instead.	2023-08-23 22:18:45 -07:00
torque	48962f27d9	add examples and integrate into build I suppose the next step will be to translate the C examples into their zig counterparts. This is also good dog food.	2023-08-21 23:51:58 -07:00

Author

SHA1

Message

Date

torque

65ab46f714

connection: eliminate String method variants

After contemplating this for a little bit, there's no point in exposing
these separately from the plain variants. Even nats.c internally calls
its plain variants after calling `strlen` on the input. Zig benefits
from having nicer pointer types than C, so we get "string" handling
for free from the fact that the standard variants take slices anyway.

2023-08-23 22:27:33 -07:00

torque

18205a5533

examples: add statistics to request_reply

I should probably write some tests instead.

2023-08-23 22:18:45 -07:00

torque

48962f27d9

add examples and integrate into build

I suppose the next step will be to translate the C examples into their
zig counterparts. This is also good dog food.

2023-08-21 23:51:58 -07:00

3 Commits