MergeDeep : fix producing [never] when merging empty tuples.
#1330
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.
Close #1200
Test case
I use
IsEqualbecause this passes uncorrectly on editor (it rejects correctly withnpm testthough).I think this might be related to this tsd issue
Undefined behavior
This is how it behaves in this PR, but is this according to the spec?
I couldn't find any test cases that verify this, even in the original codebase.
I think this might be somewhat related to this test case, though I'm not certain.
I'll add A to D test cases if they satisfy the spec.