Ignore silentNever in intersections with other meaningful constituents#60876
Open
Andarist wants to merge 1 commit intomicrosoft:mainfrom
Open
Ignore silentNever in intersections with other meaningful constituents#60876Andarist wants to merge 1 commit intomicrosoft:mainfrom
silentNever in intersections with other meaningful constituents#60876Andarist wants to merge 1 commit intomicrosoft:mainfrom
Conversation
Andarist
commented
Dec 29, 2024
Comment on lines
+17828
to
+17830
| if (type === silentNeverType) { | ||
| return includes; | ||
| } |
Contributor
Author
There was a problem hiding this comment.
This makes silentNeverType behave more like unknown in intersections. Which is definitely not correct for a never type... but a silentNeverType is really just a special marker type so it doesn't quite have to obey the rules.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I'm not confident in this at all. I'm treating this as an experiment and I wonder if extended tests can reveal some missing test cases that should be added to the codebase.
The problem is that with a
contextualTypelikeV["someArg"] | ((number | Variable<number, any>) & V["someArg"])whenVgets instantiated withsilentNeverTypethe whole thing becomes... well,silentNeverType. The repro in question is also somewhat interesting because all the involved types come fromV:In the code above
GenericTypegets instantiated withV. In general,GenericTypebit gets converted to its constraint when a contextual type of its~ property is requested. But the mapped type that iterated over stays somewhat deferred asV["someArg"]and further down the line that creates a problem.fixes #60864