There is no language level interface concept, you have to craft it yourself with the existing language features. Take a look how allocators are defined or how reader and writer works in the zig std library source
#Zig Interface and std.atomic.Queue
willow bluff
worldly wadi
im confused how do I craft it myself?
willow bluff
That's why i suggested to look at how it's done in zig std source code
allocator interface: https://github.com/ziglang/zig/blob/master/lib/std/mem/Allocator.zig
Reader interface: https://github.com/ziglang/zig/blob/master/lib/std/io/reader.zig
Writer interface: https://github.com/ziglang/zig/blob/master/lib/std/io/writer.zig
worldly wadi
im afriad these just confuse me more, what does crafting entail? How does vtables relate to this all?
willow bluff
Those are all the details that other languages hide from you. This might help you understand it better: https://youtu.be/AHc4x1uXBQE
worldly wadi
ahhh thank you will take a look
worldly wadi
btw also for the queue how do I add something to queue?
willow bluff
Seems like a pretty simple interface: https://github.com/ziglang/zig/blob/master/lib/std/atomic/queue.zig#L31
Just make sure to store the object somewhere, queue will just manage the access to the item, but it won't take care of releasing the resources as mentioned in the documentation comment
worldly wadi
im confused by the node type, How do I create a Node type to be put in the queue
willow bluff
it is bit confusing, can't explain why it was designed like that. The Node type comes from here:
https://github.com/ziglang/zig/blob/master/lib/std/linked_list.zig#L165
Always good idea to look for inline unit tests for usage examples https://github.com/ziglang/zig/blob/master/lib/std/atomic/queue.zig#L295
This isn't regular queue, it's a synchronization mechanism. The first link is to regular queue