René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Should unions and non-primitives be allowed for relational comparisons?","articleBody":"[To quote 4.19.1 of the spec](https://github.com/Microsoft/TypeScript/blob/738b26f065a4d859c19b4c417b359baf1d74900a/doc/spec.md#4193-the--------and--operators):\n\n\u003e ### \u003csection name=\"4.19.3\" is=\"a\" /\u003e4.19.3 The \u0026lt;, \u003e, \u0026lt;=, \u003e=, ==, !=, ===, and !== operators\n\u003e \n\u003e These operators require one or both of the operand types to be assignable to the other. The result is always of the Boolean primitive type.\n\u003e \n\u003e |  | Any | Boolean | Number | String | Other |\n\u003e | :-: | :-: | :-: | :-: | :-: | :-: |\n\u003e | Any | Boolean | Boolean | Boolean | Boolean | Boolean |\n\u003e | Boolean | Boolean | Boolean |  |  |  |\n\u003e | Number | Boolean |  | Boolean |  |  |\n\u003e | String | Boolean |  |  | Boolean |  |\n\u003e | Other | Boolean |  |  |  | Boolean |\n\nThis has probably unintended consequences in the case of union types:\n\n``` TypeScript\nvar x: string | number = \"hello\";\nvar y: number = 10;\nvar z: string | number = -1;\n\nif (x \u003c y \u0026\u0026 x \u003c= z) {\n}\n```\n\nThe question is: is this still desirable behavior?\n\n@ahejlsberg @RyanCavanaugh @danquirk @mhegazy @JsonFreeman\n","author":{"url":"https://github.com/DanielRosenwasser","@type":"Person","name":"DanielRosenwasser"},"datePublished":"2015-10-07T19:38:02.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":11},"url":"https://github.com/5156/TypeScript/issues/5156"}