Title: Future-proof non-aliasing/always-expanding of mapped/intersection/union/etc. types · Issue #34556 · microsoft/TypeScript · GitHub
Open Graph Title: Future-proof non-aliasing/always-expanding of mapped/intersection/union/etc. types · Issue #34556 · microsoft/TypeScript
X Title: Future-proof non-aliasing/always-expanding of mapped/intersection/union/etc. types · Issue #34556 · microsoft/TypeScript
Description: Search Terms non-aliasing types Suggestion I would like an "officially blessed" way to tell TS if it should give me a type alias, or give me an "expanded" type. (See examples) Now that this issue has been fixed, #32824 the technique I've...
Open Graph Description: Search Terms non-aliasing types Suggestion I would like an "officially blessed" way to tell TS if it should give me a type alias, or give me an "expanded" type. (See examples) Now that this issue h...
X Description: Search Terms non-aliasing types Suggestion I would like an "officially blessed" way to tell TS if it should give me a type alias, or give me an "expanded" type. (See examples) N...
Opengraph URL: https://github.com/microsoft/TypeScript/issues/34556
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Future-proof non-aliasing/always-expanding of mapped/intersection/union/etc. types","articleBody":"\u003c!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨\r\n\r\nHalf of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.\r\n\r\nPlease help us by doing the following steps before logging an issue:\r\n * Search: https://github.com/Microsoft/TypeScript/search?type=Issues\r\n * Read the FAQ, especially the \"Common Feature Requests\" section: https://github.com/Microsoft/TypeScript/wiki/FAQ\r\n\r\n-->\r\n\r\n## Search Terms\r\n\r\n\u003c!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->\r\n\r\nnon-aliasing types\r\n\r\n## Suggestion\r\n\r\n\u003c!-- A summary of what you'd like to see added or changed -->\r\n\r\nI would like an \"officially blessed\" way to tell TS if it should give me a type alias, or give me an \"expanded\" type. (See examples)\r\n\r\nNow that this issue has been fixed,\r\nhttps://github.com/microsoft/TypeScript/issues/32824\r\n\r\nthe technique I've been using to force TS to not alias a type will break when I migrate to TS 3.6/3.7\r\n\r\n## Use Cases\r\n\r\n\u003c!--\r\nWhat do you want to use this for?\r\nWhat shortcomings exist with current approaches?\r\n-->\r\n\r\nIn some cases, seeing `Mapped1\u003cT>/Intersected1\u003cT>/Unioned1\u003cT>` is better for a developer (see examples).\r\n\r\nIn other cases, seeing the full \"expanded\" type is better (see examples for `Mapped2\u003cT>/Intersected2\u003cT>/Unioned2\u003cT>`)\r\n\r\n## Examples\r\n\r\n```ts\r\ntype Identity\u003cT> = T;\r\n\r\ntype Mapped1\u003cT> = { [k in keyof T]: [T[k], \"mapped\"] };\r\ntype Mapped2\u003cT> = Identity\u003c{ [k in keyof T]: [T[k], \"mapped\"] }>;\r\n\r\ndeclare function foo1(): Mapped1\u003c{ x: string, y: number }>;\r\ndeclare function foo2(): Mapped2\u003c{ x: string, y: number }>;\r\n\r\n/*\r\nAliased, bad\r\nconst m1: Mapped1\u003c{\r\n x: string;\r\n y: number;\r\n}>\r\n*/\r\nconst m1 = foo1();\r\n/*\r\nNon-aliased, good\r\nconst m2: {\r\n x: [string, \"mapped\"];\r\n y: [number, \"mapped\"];\r\n}\r\n*/\r\nconst m2 = foo2();\r\n\r\n//==============================================================\r\n\r\ntype Intersected1\u003cT> = T & { hi: string };\r\ntype Intersected2\u003cT> = Identity\u003cT & { hi: string }>;\r\n\r\ndeclare function bar1(): Intersected1\u003c{ x: string, y: number }>;\r\ndeclare function bar2(): Intersected2\u003c{ x: string, y: number }>;\r\n\r\n/*\r\nconst i1: Intersected1\u003c{\r\n x: string;\r\n y: number;\r\n}>\r\n*/\r\nconst i1 = bar1();\r\n/*\r\nconst i2: {\r\n x: string;\r\n y: number;\r\n} & {\r\n hi: string;\r\n}\r\n*/\r\nconst i2 = bar2();\r\n\r\n//==============================================================\r\n\r\ntype Unioned1\u003cT> = T | { hi: string };\r\ntype Unioned2\u003cT> = Identity\u003cT | { hi: string }>;\r\n\r\ndeclare function baz1(): Unioned1\u003c{ x: string, y: number }>;\r\ndeclare function baz2(): Unioned2\u003c{ x: string, y: number }>;\r\n\r\n/*\r\nconst u1: Unioned1\u003c{\r\n x: string;\r\n y: number;\r\n}>\r\n*/\r\nconst u1 = baz1();\r\n/*\r\nconst u2: {\r\n hi: string;\r\n} | {\r\n x: string;\r\n y: number;\r\n}\r\n*/\r\nconst u2 = baz2();\r\n```\r\n[Playground](http://www.typescriptlang.org/play/?ts=3.7-Beta&ssl=1&ssc=1&pln=74&pc=19#code/C4TwDgpgBAkgJhAdsAlqAPAFQHxQLxSYDcAUCaJFALICGYkcAjFrgQN5QDaA1lColG4QQAewBmhALoAuLph6SANFABEAWzoMVkqAF9SFaLXoQ4AJhb5YCZGhDoOPPgKGiJmGXIXL1m09r1sUhIEAGMAGxoAJ2gxAFdEUNQRATEREUYACgBKWWMGZg4AD1kAZ2Ao-gBzZRBZRDi1ACMIKMDSMMiYqHjE5NT0sxy8v3MHKBKocsrEGqg6qAbm1vayAHoAKhIAQXCUGlLTZSaaOBJQlPKoNUYRkyYHEihnibKK6tIX+frGlqjSXTYEgbNbnS7Aa6MKxpDI5UibEgAORSAFoaHsDkcoFV0mcLogrmozLI2E8XpNONNqj4NPdtJ8XgtOEs-jTRvSSLpgaD8YSzNDBnD1ms8KKxeKJZKpdKZbKpWRDLBkK1DklTMwcFZMFAAGRQDgACxQbxmVT0BnA0BgyqiquApgsmoI8CQqAw2r1huNU3es1WIQgEWisQSSRQKSgJyiWVySvttsD9oexRN1O+i1+K0BHUDXRDfXDAijQ1j1vjdod40mVNmtR+yza2fWW15EJQtzjKsT6seX2rvqqDOeCxZrQBQJBYIJbahBCjMfhLfBfGJ+rJz37pqH6dH-05urXXyNqdmAO5U6uKH5c+iJeCaxFcqfz5fcoVlqgAFVEIWe07CFAAA++pQMePqmua5Aft+v5jP+Lq2O6QEgWBNZmk2AZBt0vRhhGJwAF4xrIMEpD2KbgWmI6Zo2QSYXmPShv0kY0PhJbET+pFjORaF1hmDb+girZQHEHYkYgZHrq8FGnpJVENuO55CSJVgEQuJCCcucSrqSR7emhALITp5InoOsn1n8Z6Tkp17MaxcJAA)\r\n\r\n## Checklist\r\n\r\nMy suggestion meets these guidelines:\r\n\r\n* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code\r\n* [x] This wouldn't change the runtime behavior of existing JavaScript code\r\n* [x] This could be implemented without emitting different JS based on the types of the expressions\r\n* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)\r\n* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).\r\n\r\n## Related\r\n\r\nhttps://github.com/microsoft/TypeScript/issues/32824#issuecomment-521127740\r\n\r\n@weswigham brought up a different way to force TS to not alias a type.\r\n\r\nI prefer my `Identity\u003cT>` trick because it doesn't create a new \"temporary\" object type.","author":{"url":"https://github.com/AnyhowStep","@type":"Person","name":"AnyhowStep"},"datePublished":"2019-10-18T09:14:04Z","url":"https://github.com/microsoft/TypeScript/issues/34556"}
| 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:a7c9a435-d5ab-3d9a-db7b-95d2e80c043b |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | DB66:34DB8F:24204FA:30504F2:6B01A34D |
| html-safe-nonce | 52e8becbd614ed6ac0bba8d7d4e1ff484424c3055b9fb0120fa413af0f047654 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJEQjY2OjM0REI4RjoyNDIwNEZBOjMwNTA0RjI6NkIwMUEzNEQiLCJ2aXNpdG9yX2lkIjoiNjg1NzAwMDEzMTYyMDc5MDUzIiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | dd993de69d9d10e1f83fcf5b6e15e26ccabfdd280f74b492e7108f92aca85af3 |
| hovercard-subject-tag | issue:508954991 |
| 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/34556/issue_layout |
| twitter:image | https://opengraph.githubassets.com/5c5e28840256a865761f77c5be0e01b4c271e5da095f4b59b876b68a3ebde114/microsoft/TypeScript/issues/34556 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/5c5e28840256a865761f77c5be0e01b4c271e5da095f4b59b876b68a3ebde114/microsoft/TypeScript/issues/34556 |
| og:image:alt | Search Terms non-aliasing types Suggestion I would like an "officially blessed" way to tell TS if it should give me a type alias, or give me an "expanded" type. (See examples) Now that this issue h... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | AnyhowStep |
| hostname | github.com |
| expected-hostname | github.com |
| None | cc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c |
| 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 | 8c77c9e8439031ad54c75a250694842892f693e1 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width