Add note about TypeScript 2 support for non-null #2
Conversation
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
Despite being a fan of Flow, I do think it's prudent for any recent comparison to include SOME features on the project timeline, including [non-nullable types](microsoft/TypeScript#7140) in version 2.
|
Thanks for the input, but there is a link to that PR for nun-nullable types in the slides already. |
|
I'm an idiot, not sure how I missed that, thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Despite being a fan of Flow, I do think it's prudent for any recent comparison to include SOME features on TypeScript's timeline, including non-nullable types in version 2. Obviously, adapt the language to whatever you think is best though.