Title: Weak type guaranties for tuples · Issue #15656 · microsoft/TypeScript · GitHub
Open Graph Title: Weak type guaranties for tuples · Issue #15656 · microsoft/TypeScript
X Title: Weak type guaranties for tuples · Issue #15656 · microsoft/TypeScript
Description: TypeScript Version: 2.3.2 I bumped into a strange behaviour wrt tuples by spotting a difference in the way type inference works with value and reference types. Code // Value types are inferred to their most specific type. const foo = 42;...
Open Graph Description: TypeScript Version: 2.3.2 I bumped into a strange behaviour wrt tuples by spotting a difference in the way type inference works with value and reference types. Code // Value types are inferred to t...
X Description: TypeScript Version: 2.3.2 I bumped into a strange behaviour wrt tuples by spotting a difference in the way type inference works with value and reference types. Code // Value types are inferred to t...
Opengraph URL: https://github.com/microsoft/TypeScript/issues/15656
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Weak type guaranties for tuples","articleBody":"**TypeScript Version:** 2.3.2\r\n\r\nI bumped into a strange behaviour wrt tuples by spotting a difference in the way type inference works with value and reference types.\r\n\r\n**Code**\r\n\r\n```ts\r\n// Value types are inferred to their most specific type.\r\nconst foo = 42; // will infer to foo: 42 instead of foo: number\r\n\r\n// Reference types infer to their most generic type.\r\nconst bar = [1, 2]; // will infer to bar: number[] instead of bar: [number, number]\r\n```\r\n\r\nThis is understandable, because `const`/`readonly` work the same way as their JS equivalents (values of reference types are mutable), so casting to the most specific type without having a way of enforcing actual immutability would cause more harm than good.\r\n\r\nAt that point I expected that explicitly typing my tuples as `[number, number]` will not only make the compiler comply (no more `number[]` is not assignable to `[number, number]`), but also give me additional type guarantees. Then I discovered that I can do the following no problem:\r\n\r\n```ts\r\nconst foo: [number, number] = [1, 2, 3];\r\n\r\nconst quux: [number, number] = [10, 11];\r\nquux[3] = 12;\r\n\r\nconst bar: [number, number] = [4, 5];\r\nbar.pop();\r\n\r\nconst baz: [number, number] = [6, 7];\r\nbaz.shift();\r\n\r\nconst qux: [number, number] = [8, 9];\r\nqux.splice(0, 1);\r\n```\r\n\r\n**Expected behaviour:**\r\nThere are probably 2 things that could be done here:\r\n\r\n1. The exact length of tuples is enforced. Property accessor disallows accessing elements outside tuple's range (currently it uses the union type for everything outside the range). This is a documented behaviour, so probably harder to amend (unless implemented with a flag).\r\n2. Mutable `Array.prototype` methods are disallowed on tuples. Virtually all of them, when called on a tuple, guarantee that you're going to end up with a value incompatible with your tuple type. The exception would be calling them with arguments that do nothing (e.g. `[1, 2].splice(0, 2)`) and calling those which add and element (e.g. `[1, 2].push(3)`).\r\n\r\n**Actual behaviour:**\r\nTuples behave like arrays with only minimum length being enforced.\r\n\r\n","author":{"url":"https://github.com/kujon","@type":"Person","name":"kujon"},"datePublished":"2017-05-08T11:04:32Z","url":"https://github.com/microsoft/TypeScript/issues/15656"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:f6a85172-df68-b753-ba7a-fbdc057919c2 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 850E:2E124E:803570:A51B8E:6B00E9F0 |
| html-safe-nonce | 3ac195c70aed77ac082c96e02b254e48226821e17f0d9e41d1aa523c3f9085c6 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI4NTBFOjJFMTI0RTo4MDM1NzA6QTUxQjhFOjZCMDBFOUYwIiwidmlzaXRvcl9pZCI6IjM2MDk1MjEzMjA4NTkwNjg5MTIiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 58e1409a836e2a786dd5957d453a8fb22d8b12291e95a909e1923657704f1b00 |
| hovercard-subject-tag | issue:227011731 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/microsoft/TypeScript/15656/issue_layout |
| twitter:image | https://opengraph.githubassets.com/6b8f803e32beafceed061051893ed98c7c0ebee46c2cc803e24b0aa07d38a8cd/microsoft/TypeScript/issues/15656 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/6b8f803e32beafceed061051893ed98c7c0ebee46c2cc803e24b0aa07d38a8cd/microsoft/TypeScript/issues/15656 |
| og:image:alt | TypeScript Version: 2.3.2 I bumped into a strange behaviour wrt tuples by spotting a difference in the way type inference works with value and reference types. Code // Value types are inferred to t... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | kujon |
| hostname | github.com |
| expected-hostname | github.com |
| None | 4ef498cbabcbe3c50befc7a5b743e7072ee770b4daf0e15e54801180d1fa91fc |
| turbo-cache-control | no-preview |
| go-import | github.com/microsoft/TypeScript git https://github.com/microsoft/TypeScript.git |
| octolytics-dimension-user_id | 6154722 |
| octolytics-dimension-user_login | microsoft |
| octolytics-dimension-repository_id | 20929025 |
| octolytics-dimension-repository_nwo | microsoft/TypeScript |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 20929025 |
| octolytics-dimension-repository_network_root_nwo | microsoft/TypeScript |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 9983dd5da06943f833c971dd5b6bc988e2858be5 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width