Title: Design Meeting Notes, 10/16/2015 · Issue #5292 · microsoft/TypeScript · GitHub
Open Graph Title: Design Meeting Notes, 10/16/2015 · Issue #5292 · microsoft/TypeScript
X Title: Design Meeting Notes, 10/16/2015 · Issue #5292 · microsoft/TypeScript
Description: N.B. these notes use the word "module" extensively, which we now use to only mean "external module" in the old parlance. I will use "namespace" to refer to "internal modules" if needed. Augmenting Types from External Modules (#5269, #416...
Open Graph Description: N.B. these notes use the word "module" extensively, which we now use to only mean "external module" in the old parlance. I will use "namespace" to refer to "internal modules" if needed. Augmenting ...
X Description: N.B. these notes use the word "module" extensively, which we now use to only mean "external module" in the old parlance. I will use "namespace" to refer to "inter...
Opengraph URL: https://github.com/microsoft/TypeScript/issues/5292
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Design Meeting Notes, 10/16/2015","articleBody":"N.B. these notes use the word \"module\" extensively, which we now use to only mean \"external module\" in the old parlance. I will use \"namespace\" to refer to \"internal modules\" if needed.\n# Augmenting Types from External Modules (#5269, #4166)\n- Bind operator is like extension methods for JS\n - But people do love `.`\n - And if you love `.`., prototype mutation is the only way to accomplish it\n- Two problems facing Rx\n - How do I make a class appear to have methods that I don't want to implement\n - Remove the check for ambientness of classes merged with interfaces (:+1:)\n - How do I make the type of a global (or module-scoped) type depend on the set of modules that are imported?\n - This is an anti-pattern, but what can you do ¯_(ツ)_/¯\n - Some very terrible workarounds exist\n - Implementation approach\n - Binder has a concept of 'scripts' which contribute to the global, and 'modules' which contribute to their local scope, along with their separate exports\n - Only ambient modules have a symbol in the global scope, which is their quoted name\n - Module _files_ never get a symbol and are not subject to merging; this is what we would need to change\n - Fix: add a canonical name to all module files so that they become mergable\n - This gets us augmentation of modules even from within other modules, which is currently disallowed\n - Q: How do you augment global types in this model?\n - A: We have a special string that means the global scope, use e.g. `declare module '/' {` or `declare module '' {`\n - Note that the types in a module would not directly visible in an interior ambient module declaration\n - Add an `import` declaration? It's weird. Maybe implicitly import them into scope... try it out and see what happens, should be OK\n - Q: How do we resolve these names?\n - A: Relative to the current file\n - Q: How do we produce these canonical names?\n - A: Need to figure that out. Doable.\n - Q: How do I refer to shadowed global types from within an ambient module inside a module?\n - A: Maybe you just don't... or refer to `\"./obs\".Observable`\n - A: Or `import { Observable } from './obs';\n - A: Or `global.Array` in the global case?\n - A: Or `interface obs.Observable\u003cT> { ... }` \u003c- nice\n - Theory that `interface foo.bar { }` always means _extending_ `bar` from the `foo` namespace\n - With special LHS semantics for `global`\n - Can I declare things here, too?\n - Yes\n - Syntax/semantics: `interface global::Foo`, `interface global.Foo`, `interface global Foo`, ?\n - `declare global var x;`\n - `declare in './obs' var x;`\n - What happens if I try to `declare in` a non-existent module?\n - It's like an ambient external module?\n - Only ambient classes could use dotted declarations\n - Speculation that we _could_ emit non-ambient classes this way\n - :+1: Conclusions\n - Allow merging of interfaces and non-ambient classes\n - `declare module 'foo' {` is allowed in modules\n - Are the containing module's symbols in scope? Yes, and the global symbols have priority\n - `declare module '../relativePath' {` is allowed in a module, but not in a script\n - Are the containing module's symbols in scope? Yes\n - `declare global {` augments the gloal scope, and is only allowed at top-level in a module (not a script)\n - Are module `import`s allowed in here? No.\n - Is `export =` allowed in here? No.\n - Are the containing module's symbols in scope? Yes\n - Rabble about declaration emitter\n - Vlad and Anders to tackle it\n","author":{"url":"https://github.com/RyanCavanaugh","@type":"Person","name":"RyanCavanaugh"},"datePublished":"2015-10-16T19:12:37Z","url":"https://github.com/microsoft/TypeScript/issues/5292"}
| 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:ae329c44-550a-df70-26f5-52090a67c3b3 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | CFB6:2679E9:D33111:11AB906:6B0101D9 |
| html-safe-nonce | 1a08ce2804617968eb7f52aaf744eed2005957d9201c498cc9ee22b8db1743b5 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJDRkI2OjI2NzlFOTpEMzMxMTE6MTFBQjkwNjo2QjAxMDFEOSIsInZpc2l0b3JfaWQiOiI0ODA3ODg0ODE2NDA4MTgzMjU3IiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | f6e810abfc782107cfe5aa36f2f58c6d753d9bf8fecdf9f5e8f72019a1967cdd |
| hovercard-subject-tag | issue:111893554 |
| 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/5292/issue_layout |
| twitter:image | https://opengraph.githubassets.com/35dd71762278c00825798b022482b322636d8094d471061789b5149391915d61/microsoft/TypeScript/issues/5292 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/35dd71762278c00825798b022482b322636d8094d471061789b5149391915d61/microsoft/TypeScript/issues/5292 |
| og:image:alt | N.B. these notes use the word "module" extensively, which we now use to only mean "external module" in the old parlance. I will use "namespace" to refer to "internal modules" if needed. Augmenting ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | RyanCavanaugh |
| hostname | github.com |
| expected-hostname | github.com |
| None | cb7fa109eca7d4156c889f474306b0e91336055e9adf8fd4684b61e49094d124 |
| 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 | 2b59d31a4e44f08b7af67a4b67f8fd0af3befe2a |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width