It was an oversight that I didn’t build it in 0.10. this feature will come in 0.11
ityonemo
ityonemo
actually in the meantime, you can probably (haven’t tried it, kinda guessing) get the result you want by doing:
~Z"""
pub usingnamespace @import("file-to-import.zig");
"""
0
jeremy_c
Just a FYI, when I tried the pub usingnamespace trick, I get:
** (KeyError) key :pub not found
(zig_parser 0.1.9) lib/zig.parser.ex:272: Zig.Parser.put_opt/3
(zig_parser 0.1.9) lib/zig.parser/top_level_decl.ex:5: Zig.Parser.TopLevelDecl.post_traverse/5
(zig_parser 0.1.9) Zig.Parser."TopLevelDecl__22"/6
(zig_parser 0.1.9) Zig.Parser."ContainerDeclarations__4"/6
(zig_parser 0.1.9) Zig.Parser."ContainerMembers__0"/6
(zig_parser 0.1.9) Zig.Parser."Root__4"/6
(zig_parser 0.1.9) Zig.Parser.parser__1/6
(zig_parser 0.1.9) Zig.Parser.parser/2
(zig_parser 0.1.9) lib/zig.parser.ex:179: Zig.Parser.parse/1
(zigler 0.10.3) lib/zig/compiler.ex:85: Zig.Compiler.compile/4
(zigler 0.10.3) expanding macro: Zig.Compiler.__before_compile__/1
It’s OK if the feature is coming in 0.11. Thanks for giving it a shot!
1
zookzook
Many thanks for the great work on Zigler — it really opens up exciting new possibilities!
Up to now, I’ve been using Rustler and Rust to offload certain tasks.
Rust is powerful, but I often found it a bit tricky and more complicated than I’d like.
That’s why I recently started exploring Zig and Zigler.
As a little learning exercise, I built an IPv4 trie in Zig. It can be used in Phoenix, for example, to block or allow specific host addresses.
Here’s the link to the repo: ZigDemo
4
venkatd
We’ve been using Zigler/Zig in production and I love how seamless the experience is.
We opted for Zig over Rust for personal preferences. I think Zig is closer to C while Rust is closer to C++. We’re more C-kind of personality.
It also comes in handy when trying to integrate with 3rd party C libraries.
3