Title: Granular inference for generic function type arguments · Issue #20122 · microsoft/TypeScript · GitHub
Open Graph Title: Granular inference for generic function type arguments · Issue #20122 · microsoft/TypeScript
X Title: Granular inference for generic function type arguments · Issue #20122 · microsoft/TypeScript
Description: Consider the following function, based on this StackOverflow question: // Take a type and some properties to pluck from it. Ensure only functions can be plucked. type PluckFuncs = Open Graph Description: Consider the following function, based on this StackOverflow question: // Take a type and some properties to pluck from it. Ensure only functions can be plucked. type PluckFuncs = X Description: Consider the following function, based on this StackOverflow question: // Take a type and some properties to pluck from it. Ensure only functions can be plucked. type PluckFuncs = <TComponent ex...
Opengraph URL: https://github.com/microsoft/TypeScript/issues/20122
X: @github
Domain: github.com
Links:
Viewport: width=device-width
Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Granular inference for generic function type arguments","articleBody":"Consider the following function, based on [this StackOverflow question](https://stackoverflow.com/questions/47359713/filter-on-keyof-type-parameter-in-typescript/47359891):\r\n\r\n```ts\r\n// Take a type and some properties to pluck from it. Ensure only functions can be plucked.\r\ntype PluckFuncs =\r\n \u003cTComponent extends {[P in TKey]: Function }, TKey extends string>\r\n (props: TKey[]) => any\r\n```\r\n\r\nCurrently it is not possible to use this function ergonomically. You must always supply both type arguments, even though `TKey` can comfortably be inferred from `props`.\r\n\r\nIt should be possible to invoke a generic function and specify a named subset of the type parameters, i.e. `pluckFuncs\u003cTComponent = { a: () => string }>(['a'])`, and have inference decide (or fail to decide) the remaining type parameters (in this case `TKey`).\r\n\r\nIn terms of the desired semantics, the inference should treat explicit type arguments no differently from the types of the function's value arguments, except for the fact that no values will be forthcoming at the invocation site. \r\n\r\nIn other words, doing this:\r\n\r\n```ts\r\ntype PluckFuncs =\r\n \u003cTComponent extends {[P in TKey]: Function }, TKey extends string>\r\n (props: TKey[]) => any\r\n\r\ndeclare const pluckFuncs: PluckFuncs\r\n\r\npluckFuncs\u003c{ a: () => string }>(['a']) // Won't work, forced to explicitly specify `TKey`\r\n```\r\n\r\nshould behave no differently from when I just add a dummy value argument to serve as an inference site:\r\n\r\n```ts\r\ntype PluckFuncs =\r\n \u003cTComponent extends {[P in TKey]: Function }, TKey extends string>\r\n (props: TKey[], dummy?: TComponent) => any\r\n\r\ndeclare const pluckFuncs: PluckFuncs\r\n\r\npluckFuncs(['a'], undefined as { a: () => string }) // Compiler is happy with this though\r\n```\r\n\r\n## Aside:\r\n\r\nThe workaround one might come up with is to give `TKey` a default of `keyof TComponent`:\r\n\r\n```ts\r\ntype PluckFuncs =\r\n \u003cTComponent extends {[P in TKey]: Function }, TKey extends string = keyof TComponent>\r\n (props: TKey[]) => any\r\n```\r\n\r\nThis *seems* like a sensible thing to do, but isn't really the semantics we're looking for. When you try to use it:\r\n\r\n```ts\r\ndeclare const pf: PluckFuncs\r\n\r\ninterface TestProps {a: number, b: Function, c: () => number}\r\n\r\n// Good - missing property, should be an error\r\npf\u003cTestProps>(['d'])\r\n\r\n// Good - non-function property plucked, should be an error\r\npf\u003cTestProps>(['a'])\r\n\r\n// Bad - all plucked properties extend `Function`, but this is nevertheless an error\r\npf\u003cTestProps>(['b', 'c'])\r\n\r\n// We end up needing `TestProps` to not have any non-function properties whatsoever\r\n\r\n// ...or to specify the second type argument explicitly\r\npf\u003cTestProps, 'b' | 'c'>(['b', 'c'])\r\n```\r\n\r\nWhat's happened is that we only have one degree of freedom here. Defaulting `TKey` to a type derived from `TComponent` has ended up imposing an additional constraint on `TComponent` instead of constraining the parameter that uses `TKey` with respect to `TComponent`.\r\n\r\nI think the behavior seen above is valid, and that default type arguments are a totally different ballgame. They shouldn't be mixed up in our problem with independent inference of type parameters when instantiating abstract function types.","author":{"url":"https://github.com/masaeedu","@type":"Person","name":"masaeedu"},"datePublished":"2017-11-17T23:48:00Z","url":"https://github.com/microsoft/TypeScript/issues/20122"}
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:5ca01953-2d11-6157-98f4-34afdde11e9b current-catalog-service-hash 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 request-id BC0C:ADA9D:345096F:431E194:6B01D4DF html-safe-nonce b2a59c145a6838a8095eb4446e59bc4ae4a068d2ba56d18321224f01403496ec visitor-payload eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCQzBDOkFEQTlEOjM0NTA5NkY6NDMxRTE5NDo2QjAxRDRERiIsInZpc2l0b3JfaWQiOiIzODU0MDE0OTYxNjgxNTg0MzEiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== visitor-hmac acca400a01e559e549527b9c7eab42432e97cf9b855b5e8391afdfbec18a5738 hovercard-subject-tag issue:275029522 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/20122/issue_layout twitter:image https://opengraph.githubassets.com/e73ed974fbcc1defeab76e96a1965ed54dd064b90a6e21ab3738861fcbcf81b4/microsoft/TypeScript/issues/20122 twitter:card summary_large_image og:image https://opengraph.githubassets.com/e73ed974fbcc1defeab76e96a1965ed54dd064b90a6e21ab3738861fcbcf81b4/microsoft/TypeScript/issues/20122 og:image:alt Consider the following function, based on this StackOverflow question: // Take a type and some properties to pluck from it. Ensure only functions can be plucked. type PluckFuncs = og:image:width 1200 og:image:height 600 og:site_name GitHub og:type object og:author:username masaeedu 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
URLs of crawlers that visited me.