什么是静态类型检查，有什么好处
What is static type checking and how can developers benefit from it
一句话：不运行代码，只靠分析源码就找出类型不匹配的地方。 「静态」的意思就是「在编译期，而非运行期」。
四个具体收益（要给例子，别空谈）：
- 错误提前——
user.nmae拼错、 忘了处理null、 给函数传少了参数，在编辑器里就红了， 而不是上线后用户报给你。 - 类型即文档—— 函数签名说明了它要什么、给什么。而且这份文档不会过期， 因为改了代码不改类型就编译不过。
- 重构有底气—— 改一个字段名， 所有受影响的地方都会报错。这是 TS 最被低估的价值， 在大项目里比「防 bug」更实用。
- IDE 能力—— 精确补全、跳定义、 安全重命名。
局限（说出来才显得懂）：它只保证「类型对」，不保证「逻辑对」—— 类型全过的代码照样能算错工资。 而且它管不到运行时的外部数据（见 #355），所以类型检查不能替代测试。
会追问：「strict 模式开不开？」——新项目一定开。 最有价值的是strictNullChecks—— 它把「忘了判空」这一整类 运行时错误变成编译错误。
顺带一个真实例子：React 那门课的源项目npm run build 就是因为tsc 报了 10 个错误而失败的 （测试文件缺 vitest 全局类型）—— 这说明类型检查是构建的一部分， 不是可选的 lint。
In one line: without running the code, purely by analysing the source, it finds places where the types do not line up. “Static” just means “at compile time, not at run time”.
Four concrete benefits — give examples, do not speak in the abstract:
- Errors surface earlier — a typo like
user.nmae, a forgottennullcase, a missing argument: they go red in the editor instead of arriving as a user report after release. - Types are documentation — a signature says what it wants and what it gives back. And this documentation cannot go stale, because changing the code without changing the types fails the build.
- Refactoring with confidence — rename one field and every affected place errors. This is TS’s most underrated value, and on a large codebase it is more useful than bug prevention.
- Editor power — accurate completion, jump to definition, safe rename.
The limits — saying them is what shows you get it: it only guarantees the types are right, not that the logic is — fully typed code can still calculate the wrong salary. And it has no reach over external data at runtime (see #355), so type checking is not a substitute for tests.
Follow-up: “Do you turn on strict?” — always on a new project. The most valuable piece is strictNullChecks — it turns an entire class of “forgot the null check” runtime errors into compile errors.
A real example to go with it: npm run build on the source project for the React course fails precisely because tsc reports 10 errors (the test file is missing the vitest globals) — which shows type checking is part of the build, not an optional lint.