Support unknown and never types - #233
Open
devSparkle wants to merge 1 commit into
Open
Conversation
Add support for `unknown` and `never` built-in types in language syntax.
devSparkle
changed the title
|
surprised this doesnt have any attention |
Owner
|
This change only adds special syntax highlighting for those types, does not adds the types nor implements their behaviour. |
Author
Could you point to where this could be implemented? It's also my understanding that this change would at the very least remove the warning type annotations, which is the very least we could do. |
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
3 participants
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.
This PR adds support for
unknownandneverbuilt-in types in language syntax. This partially fixes #232.