Microsoft/TypeScript
在 GitHub 查看Differing user-defined type guard and 'typeof' type guard behaviour when narrowing 'any'
Open
#6,015 建立於 2015年12月9日
Effort: ModerateHelp WantedSuggestion
倉庫指標
- Star
- (48,455 star)
- PR 合併指標
- (平均合併 6天 17小時) (30 天內合併 9 個 PR)
描述
In the below code, using a typeof type guard and an equivalent (I thought) user-defined guard, only one error is produced.
var y: any;
// Built-in type guard
if (typeof y === "string") {
y.hello = true; // Correct error - 'hello' does not exist on type string
}
// Equivalent user-defined type guard
function f(x: any): x is string {
return typeof x === "string";
}
if (f(y)) {
y.hello = true; // No error with user-defined guard
}
Playground demo. Looks like user-defined type guards won't narrow from any, in any circumstances, as far as I can tell.