3 ms·

I "don't know" because zig 0.14 is not released yet and anything could happen but I DO know that imports do not currently require the build system. And I THINK

I "don't know" because zig 0.14 is not released yet and anything could happen but I DO know that imports do not currently require the build system. And I THINK that's because the core parts of the build system (including binding imports) are dependent on the command line anyways. So I am ASSUMING that property will be invariant when the c @import gets implemented, and my "don't know" is merely being explicit about that assumption. You are the one coming from a place of ignorance here, and your refusal to acknowledge that you might be wrong makes me suspect your argument is not being made in good faith.

jay-barronville 2y ago
> You are the one coming from a place of ignorance here, and your refusal to acknowledge that you might be wrong makes me suspect your argument is not being made in good faith. You’re making a lot of “assumptions” when you could just read the GitHub issue regarding this change, written by Andrew himself, titled “move @cImport to the build system” [0]. By the way, please note that I not only write Zig code almost daily, I’ve personally contributed to the Zig build system. [0]: https://github.com/ziglang/zig/issues/20630 https://github.com/ziglang/zig/issues/20630
- throwawaymaths 2y ago
  Andrew responded in that thread to some more recent comments and made it clear that it will be possible to do all the things from the client without build.zig, (apparently not in one command though)