Exactly. Leaving off the return type annotation is just asking for trouble, and this example proves it.
And the actual type of the const won't be `string | number` -- it will be `any`.
MaulingMonkey[1] has the right idea, though.
And the actual type of the const won't be `string | number` -- it will be `any`.
MaulingMonkey[1] has the right idea, though.
I suppose the reasoning is that, when adding types to js, this is exactly the kind of bad behaviour you want to catch. But I'm not sure, perhaps there are just technical implications for not inferring union return types.