Fix intersection inference #18363
Merged
Fix intersection inference #18363
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DanielRosenwasser
approved these changes
Sep 9, 2017
| declare const a: { prop: string } & { prop: number }; | ||
| declare const b: { prop: string & number }; | ||
|
|
||
| f(a); // string & number |
There was a problem hiding this comment.
Consider using more realistic types for this test given that we've already been thinking about removing empty intersections types.
|
Does this change affect or undo #14829 (comment) ? |
RyanCavanaugh
approved these changes
Sep 11, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #18354.
Verified that there are no changes to RWC baselines.
@RyanCavanaugh Would you mind giving the fourslash changes (related to JSX inference) a look? Best I can tell they are correct.