`const wrong = () => (1 < 3) as true // type: () => true` this should be an error. about typescript HOT 9 CLOSED

I'm amazed that people figured out what this issue meant. My brain was imploding trying to understand what could possibly have been the bug: "Why would the () => part matter here? Why is the desired behavior just 'an error' without mentioning, like, what kind of error? Why wouldn't you be allowed to narrow from boolean to true in a type assertion? Wait, has 3 cut in front of 1 and 2 in the number line again? Am I... am I dreaming? This is a dream, isn't it?"

from typescript.

3 is always cutting in front of 1 and 2, he thinks he's so important having his visage plastered everywhere. Still better than that jerk 7. 6 still needs therapy to this day after witnessing t h e i n c i d e n t

from typescript.

This is working as intended. Using a type assertion you tell the compiler "shh.. trust me, it's this type, I know what I'm doing..."

@KDwevedi They surely mean the 1 > 3 case.

from typescript.

Maybe I'm just slow today, but why should this trigger an error?

from typescript.

...I was expecting the above code to be an error, since the 1 < 3 is always false.

Why is 1 < 3 false? < is just the less than comparison operator, correct?

from typescript.

@dragomirtitian This is just a guess but maybe OP expects an error because 2 < 3 is always false? But then false as true isn’t an error either so…

from typescript.

I should have been more clear.

as @fatcerberus mentioned, I was expecting the above code to be an error, since the 1 < 3 is always false.

from typescript.

Note that all of these are valid...

const a = false as true;
const b = 'x' as 'y';
const c = 1 as 2;

from typescript.

This issue has been marked as "Working as Intended" and has seen no recent activity. It has been automatically closed for house-keeping purposes.

from typescript.