in operator shouldn't narrow {} originating in unknown#50610
Conversation
|
@typescript-bot test this |
|
Heya @ahejlsberg, I've started to run the parallelized Definitely Typed test suite on this PR at 517777d. You can monitor the build here. |
|
Heya @ahejlsberg, I've started to run the diff-based user code test suite on this PR at 517777d. You can monitor the build here. Update: The results are in! |
|
Heya @ahejlsberg, I've started to run the extended test suite on this PR at 517777d. You can monitor the build here. |
|
Heya @ahejlsberg, I've started to run the diff-based user code test suite on this PR at 517777d. You can monitor the build here. Update: The results are in! |
|
Heya @ahejlsberg, I've started to run the abridged perf test suite on this PR at 517777d. You can monitor the build here. Update: The results are in! |
|
@ahejlsberg Here they are:Comparison Report - main..50610
System
Hosts
Scenarios
Developer Information: |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
@ahejlsberg Here are the results of running the user test suite comparing Everything looks good! |
|
@ahejlsberg Here are the results of running the top-repos suite comparing Everything looks good! |
|
@typescript-bot cherry-pick this to release-4.8 |
|
Heya @andrewbranch, I've started to run the task to cherry-pick this into |
|
Hey @andrewbranch, I've opened #50612 for you. |
|
What was the cause of #50531? It’s weird that |
|
It’s that weird |
Component commits: 908548e 'in' operator shouldn't narrow {} originating in unknown 517777d Add regression test Co-authored-by: Anders Hejlsberg <[email protected]>
Fixes #50531.
This is a targeted fix for the exact issue in #50531. It doesn't address other known issues with the
inoperator.