Title: Design Meeting Notes for 1/29/2016 · Issue #6735 · microsoft/TypeScript · GitHub
Open Graph Title: Design Meeting Notes for 1/29/2016 · Issue #6735 · microsoft/TypeScript
X Title: Design Meeting Notes for 1/29/2016 · Issue #6735 · microsoft/TypeScript
Description: Different modifiers for get/set accessors (#2845) People want private/protected set accessors with public get accessors. Or combinations thereof. Why can't people use private backing fields with a readonly accessor? Because that's annoyi...
Open Graph Description: Different modifiers for get/set accessors (#2845) People want private/protected set accessors with public get accessors. Or combinations thereof. Why can't people use private backing fields with a ...
X Description: Different modifiers for get/set accessors (#2845) People want private/protected set accessors with public get accessors. Or combinations thereof. Why can't people use private backing fields wit...
Opengraph URL: https://github.com/microsoft/TypeScript/issues/6735
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Design Meeting Notes for 1/29/2016","articleBody":"# Different modifiers for get/set accessors (#2845)\n- People want `private`/`protected` set accessors with `public` get accessors.\n - Or combinations thereof.\n- Why can't people use `private` backing fields with a readonly accessor?\n - Because that's annoying.\n- We'd need to add modifiers.\n- \"Modifier salad\"\n- Doesn't really give you the encapsulation that you wanted.\n - \"I meant `public`, but only to _certain assemblies_.\n - Now you need friend assemblies.\n - Descends into madness.\n- Conclusion: let's see how people use `readonly`.\n# Overloads and Union Types (#1805)\n\n``` ts\ndeclare function alpha(x: number): void;\ndeclare function alpha(x: string): void;\n\ndeclare function beta(x: number | string): void;\n\ninterface SomeInterfaceA {\n foo(x: number): void;\n foo(x: string): void;\n}\n\n\ninterface SomeInterfaceB {\n foo(x: number | string ): void;\n foo(x: string): void;\n}\n\nclass AlphaImpl implements SomeInterfaceA {\n foo(x: number | string): void {\n alpha(x); // error because `string | number` is not compatible\n // with the first param of either overload\n\n beta(x); // okie dokey \n }\n}\n```\n- Do we \"tell\" people not to use overloads instead of unions?\n - How?\n - We currently don't have any guidance, so we should do that.\n - But it's not like people always look up guidance when they start working on a `.d.ts` file.\n - Just tell people only use overloads when necessary.\n- People get the intuition that we should \"do the right thing\".\n - But if there's more than one parameter, this \"only sometimes works\".\n - \"People generally don't expect the case of more than one parameter to work.\"\n - So we special case that?\n - Sounds terrible.\n- This is similar to the \"specialized string\" case.\n- Should we go through DefinitelyTyped?\n- It might be possible to write a linting rule for this.\n- Conclusion: nada, give guidance.\n# Abstract methods with callbacks (#5591)\n- Want to be able to say \"Whoever `implements`/`extends` me must declare a property named `blah`.\"\n- Proposal is\n - to just allow `abstract` on properties.\n - to ensure class extending an `abstract` class must implement all `abstract` properties.\n- What is the distinction between a method and a property here? \n- How does `readonly` and `abstract` mix?\n- `public static abstract readonly`\n - Aha, `static` is not valid with `abstract`.\n - Our users will be so disappointed they won't be able to write that.\n# Using string indexers with `string`-intersected types (#4372, #5599)\n- Motivation is:\n \n ``` ts\n type Path = string & { __somePathThing: void };\n ```\n- People shouldn't do that.\n - Because it's just a hack.\n - But it's useful.\n - So let's make it not a hack.\n- Really you want a \"fresh type\".\n - How do you express that?\n - Like this?\n \n ``` ts\n type InternedString = new string;\n ```\n \n or maybe\n \n ``` ts\n type InternedString = tagged string;\n ```\n - `InternedString` is assignable to `string`.\n - `string` would not be assignable to `InternedString`.\n - How do types compose?\n \n ``` ts\n type InternedString = new string;\n type Path = new string;\n ```\n - How do I create an interned path?\n - Intersection types?\n - What is the quick info for this?\n - `tagged string` would be horrible.\n - What's the point of `tagged string` anywhere other than a type alias?\n - Why don't we just create a new declaration instead of piggybacking on type aliases? (e.g. `newtype`)\n - These declarations are nominal anyway.\n - That might just be what we want.\n - But why just these declarations?\n - Do we just want a construct that always generates a globally unique or \"fresh\" type?\n - Something like this:\n \n ``` ts\n type Path = string & ????;\n \n class Foo {\n ????\n }\n ```\n \n where `????` is that globally unique or \"fresh\" type.\n - Maybe `????` is `new` or something.\n - How would a fresh type propagate with aliases?\n \n ``` ts\n type Tag = new; // or 'unique' or whatever\n var x: Tag;\n var y: Tag;\n ```\n - Do `A` and `B` have identical types?\n - Would we only allow this on primitives and object types?\n - Why not unions/intersections?\n - No clear reason why, but how do you work with this?\n - But people don't want to use a tag for every class. They just want nominal.\n \n ``` ts\n unique interface PathTag {\n }\n \n unique class Foo {\n \n }\n unique type Path = string;\n ```\n - Uh-oh, what about type literals?\n \n ``` ts\n var x: unique { }; // wat\n ```\n - Restrict this to _declarations_ and this becomes less insane, easier to implement.\n- **_So back to the original question!**_\n- Would all those zany new types intersected with `string` still be allowable in an index signature?\n - Probably. :+1:\n","author":{"url":"https://github.com/DanielRosenwasser","@type":"Person","name":"DanielRosenwasser"},"datePublished":"2016-01-29T21:26:08Z","url":"https://github.com/microsoft/TypeScript/issues/6735"}
| 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:4c93b148-21bf-4f96-3ce6-f2c186df36ee |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | EC06:187C1E:1F8BA2:29DB83:6B0189C6 |
| html-safe-nonce | e629b9ea0f0a107e3512aef3c2996a553aba88f1ff87b5c369a5b25b77fe3f33 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFQzA2OjE4N0MxRToxRjhCQTI6MjlEQjgzOjZCMDE4OUM2IiwidmlzaXRvcl9pZCI6Ijg4MDI2MTUyMjM5MDAwMTUwNDYiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 703a7f0de861b2e4b2998f0f96878f82481bd7ed01f07470e3dea008406e00f4 |
| hovercard-subject-tag | issue:129886606 |
| 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/6735/issue_layout |
| twitter:image | https://opengraph.githubassets.com/c9f972337c802d7b24d4b99402830ac4a384440c3fcf01205c3ae373172100d0/microsoft/TypeScript/issues/6735 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/c9f972337c802d7b24d4b99402830ac4a384440c3fcf01205c3ae373172100d0/microsoft/TypeScript/issues/6735 |
| og:image:alt | Different modifiers for get/set accessors (#2845) People want private/protected set accessors with public get accessors. Or combinations thereof. Why can't people use private backing fields with a ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | DanielRosenwasser |
| 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