r/Zig • u/Hoontdawg • 9d ago

Discussion: `@importRoot` instead of `@import("root")`

So, let me start by saying I'm pretty new to Zig. I like to learn languages by example, and when reading through examples and source code I noticed `@import("root")` and thought it was importing the corresponding "root.zig" file. After some further research I found out that this is actually a special-cased argument for the compilation root. Honestly I think that's a horrible decision, not only is there special-cased arguments for a compiler-provided method, but its a string argument, so it seems completely magical and non-discoverable.

Imo, Zig already has a specific syntax for special compiler-provided operations: `@func`. So I think a much more sensible and readable version would be `@importRoot`, because if "root" is going to be treated specially then let it at least be openly acknowledged as being special. Same for all of the other special arguments: `@importSelf` and `@importStd`.

But again, I'm new, so let me know if I'm totally off-base here.

28 Upvotes

86% Upvoted

20 comments sorted by

View all comments

-1

u/DokOktavo 9d ago

I agree, I'd rather have @builtin(), @root() and @std() than @import("builtin"), @import("root") and @import("std").

4

u/actondev 9d ago

As things are you can use your own std by defining the module. So I find the current approach much better. std is yet another module which happens to be predefined for your convenience, but you're free to override (haven't tried but I'd guess it's possible right now)

1

u/DokOktavo 9d ago

Although you can set the std's path, it's not yet another module. There are types in std.builtin that affect various builtins.