Docs: "Type assertion" vs "asserts" keyword

Hey there!

I’m updating Programming TypeScript to include assertions in control flow analysis, and was looking for guidance about naming.

Type assertions (x as T) and assertions in control flow analysis (asserts x is T) are similarly named. What’s a good way to call these these features, in a way that doesn’t confuse people and aligns with the way the TS team is communicating it?

A couple of ideas:

1. Rename x as T to “type coercion” or “type casting" (even though it’s not a runtime behavior), and call asserts x is T a “type assertion”
2. Keep x as T as-is (“type assertion”), and call asserts x is T a “user-defined type assertion”, similar to a “user-defined type guard”

Thanks!

首先审阅链接的 pull request 32695，以及 issue 中关于 x as T 与 asserts x is T 的讨论。达成一项与 TypeScript 的沟通方式一致、并能指导 Programming TypeScript 更新的统一命名约定，即视为完成。