Uh oh!
There was an error while loading. Please reload this page.
Fix support for intersections in template literal placeholder types - #56434
Conversation
Anders Hejlsberg (ahejlsberg)
commented
Nov 16, 2023
TypeScript Bot (@typescript-bot) test top100 |
Heya Anders Hejlsberg (@ahejlsberg), I've started to run the tsc-only perf test suite on this PR at ca7e9c4. You can monitor the build here. Update: The results are in! |
Heya Anders Hejlsberg (@ahejlsberg), I've started to run the diff-based user code test suite on this PR at ca7e9c4. You can monitor the build here. Update: The results are in! |
Heya Anders Hejlsberg (@ahejlsberg), I've started to run the diff-based top-repos suite on this PR at ca7e9c4. You can monitor the build here. Update: The results are in! |
Heya Anders Hejlsberg (@ahejlsberg), I've started to run the parallelized Definitely Typed test suite on this PR at ca7e9c4. You can monitor the build here. Update: The results are in! |
TypeScript Bot (typescript-bot)
commented
Nov 16, 2023
Anders Hejlsberg (@ahejlsberg) Here they are:CompilerComparison Report - baseline..pr
System info unknown Hosts
Scenarios
Developer Information: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
TypeScript Bot (typescript-bot)
commented
Nov 16, 2023
Anders Hejlsberg (@ahejlsberg) Here are the results of running the user test suite comparing There were infrastructure failures potentially unrelated to your change:
Otherwise... Something interesting changed - please have a look. Details
|
TypeScript Bot (typescript-bot)
commented
Nov 16, 2023
Hey Anders Hejlsberg (@ahejlsberg), the results of running the DT tests are ready. |
TypeScript Bot (typescript-bot)
commented
Nov 16, 2023
Anders Hejlsberg (@ahejlsberg) Here are the results of running the top-repos suite comparing Everything looks good! |
Uh oh!
There was an error while loading. Please reload this page.
TypeScript Bot (@typescript-bot) pack this |
Heya Daniel Rosenwasser (@DanielRosenwasser), I've started to run the tarball bundle task on this PR at b464619. You can monitor the build here. |
Hey Daniel Rosenwasser (@DanielRosenwasser), I've packed this into an installable tgz. You can install it for testing by referencing it in your and then running There is also a playground for this build and an npm module you can use via |
Jake Bailey (@jakebailey)Daniel Rosenwasser (@DanielRosenwasser) So, there's this beauty: typeGoo<T>={[key: `abc${"def"&{tag: T}}`]: string;}typeT0=Goo<void>;// Index signature key type not instantiated so type parameter leaksBy design we don't instantiate index signature key types (that's what mapped types are for), but that in turn means we really can't permit anything generic in tag types. But we have no guaranteed way of detecting whether an object type contains something generic. I should say that there's nothing particularly dangerous about the leaked type parameter (it's just a type that isn't compatible with anything but itself), but it's certainly esthetically displeasing. Starting to seem like we just want to strip tags in template literal placeholders. |
Hmm, the leaking type parameter issue isn't actually anything new: typeLeak<T>={[key: string&{tag: T}]: string;}typeT0=Leak<void>;// Index signature key type not instantiated so type parameter leaksI seem to recall us discussing this at some point in the past but can't find anything. As I said above, it's harmless, but certainly doesn't look right. |
TypeScript Bot (@typescript-bot) cherry-pick this to release-5.3 |
Heya Daniel Rosenwasser (@DanielRosenwasser), I've started to run the task to cherry-pick this into |
TypeScript Bot (typescript-bot)
commented
Nov 21, 2023
Hey Daniel Rosenwasser (@DanielRosenwasser), I've opened #56491 for you. |
…e-5.3 (#56491) Co-authored-by: Anders Hejlsberg <andersh@microsoft.com>
Implements the changes discussed here and fixes#54177 according to our design meeting discussion.
Fixes#54177.