-
Notifications
You must be signed in to change notification settings - Fork 12.9k
Use strict subtype relation in getCommonSupertype
#61903
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR experiments with using a strict subtype relation in the computation of a common supertype.
- Switched from isTypeSubtypeOf to isTypeStrictSubtypeOf in reduceLeft for type comparison.
- Aims to leverage structural subtype relations for improved type accuracy.
Comments suppressed due to low confidence (1)
@typescript-bot test it |
Hey @ahejlsberg, the results of running the DT tests are ready. Everything looks the same! |
@ahejlsberg Here are the results of running the user tests with tsc comparing Something interesting changed - please have a look. Details
|
@ahejlsberg Here they are:
tscComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
Developer Information: |
@ahejlsberg Here are the results of running the top 400 repos with tsc comparing Something interesting changed - please have a look. Details
|
Experiment to see effects of using strict subtype relation in
getCommonSupertype
.