0Pricing
Zig Academy · 课时

编译时验证与 @compileError

用清晰的消息使构建失败

编译时验证与 @compileError 是 CoddyKit 上的免费 Zig Academy 课时。 这是第 3 节课,共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Zig Academy 学习路径的一部分,你的进度在网页和 CoddyKit 应用中同步。 Zig Academy 课程共包含 4 节课。

本课时的部分内容尚未翻译,以英文显示。

Catch Mistakes Before Run Time

Zig lets you reject bad usage while the code compiles. The built-in @compileError stops the build with a message you write. 🛑

Fail with a Clear Message

@compileError takes a comptime string and aborts compilation, printing exactly that text so the caller knows what went wrong.

@compileError("this type is not supported");

Guard a Generic Function

Inside a comptime branch you can reject unwanted types. Here only integers pass; anything else hits @compileError at the call site.

if (@typeInfo(T) != .Int) {
    @compileError("T must be an integer");
}

Errors Point at the Caller

A comptime check runs when the function is instantiated, so the error appears where the wrong type was actually passed in.

Assert Facts with comptime

For simple invariants, comptime assert stops the build when a condition is false, similar to a runtime assert but earlier.

comptime std.debug.assert(@sizeOf(T) <= 8);

Check for a Declaration

Use @hasDecl to confirm a type provides a method or constant before you call it, then fail clearly if it does not.

if (!@hasDecl(T, "init")) {
    @compileError("T needs an init function");
}

Check for a Field

Likewise @hasField tells you whether a struct has a named field, which is handy when validating shapes at compile time.

const ok = @hasField(Config, "port");

Build Messages from Type Names

Combine @typeName with std.fmt to embed the offending type in your message, giving callers a precise, readable error.

@compileError("unsupported type: " ++ @typeName(T));

Strings Join at Compile Time

The ++ operator concatenates comptime strings, so you can compose detailed error text without any heap allocation.

Zero Runtime Cost

All of this validation happens during compilation. A program that builds successfully carries no checking overhead at run time. ⚡

Better Than a Runtime Crash

Comptime validation turns a possible crash into a friendly build-time message, so misuse is caught early and explained well.

Quick Check

You want to abort the build with a custom message when a type is unsupported. What do you call?

Recap

@compileError plus checks like @hasDecl and comptime assert reject bad usage during the build, with zero runtime cost. 🎯

常见问题解答

「编译时验证与 @compileError」课时是免费的吗?

是的 — 「编译时验证与 @compileError」的完整文本可在网页上免费阅读。要进行交互式练习(内置代码编辑器和全天候 AI 导师)并解锁 Zig Academy 课程的其余内容,请升级到 CoddyKit PRO。 Zig Academy 课程共包含 4 节课。

「编译时验证与 @compileError」这节课中我会学到什么?

用清晰的消息使构建失败 你通过在浏览器中直接运行的动手代码来练习 Zig Academy,全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Zig Academy 需要有经验吗?

无需任何先前经验。CoddyKit 上的 Zig Academy 课程适合初学者到高级学习者,你可以从这里开始或从头开始,按照自己的节奏学习。 这是第 3 节课,共 4 节。

「编译时验证与 @compileError」课时需要多长时间?

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动,所以你能稳步进步,并在网页和应用中从离开的地方继续。

我能在这节 Zig Academy 课中编写并运行代码吗?

能。每节 Zig Academy 课都包含内置代码编辑器,你可以在浏览器中直接编写并运行真实代码,并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

  1. 使用 @typeInfo 反射字段
  2. 使用 @Type 构建类型
  3. 编译时验证与 @compileError
  4. 使用 comptime 生成代码
← 返回 Zig Academy