This repository was archived by the owner on Oct 12, 2022. It is now read-only.
Emphasize that void accepts null unless strictNullChecks #1096
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
|
👍 works for me, thanks @wataash |
wataash
referenced
this pull request
Aug 22, 2019
1. Point out that 'any' disables checking whereas 'Object' does not. 2. Point out that you can define variables of type 'void' but they can only be assigned 'undefined'.
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.
Though this specification was written in #1053, I still got confused when I read the section "Void":
And I had stayed confused for 10 minutes until I carefully read the next section (Null and Undefined).
This changes remove the time window of confusing between these two sections, complementing #1053.