let x?
allows initial undefined
value + type inference; let x? = y
for simple y
#1654
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.
Previously,
let x?
compiled to the invalid TypeScriptlet x?
. Now it compiles tolet x = undefined
. As this playground shows, this seems to allow for the initialundefined
value (no error about access before initialized) as well as type inference.This PR also makes
let x? = 5
compile tolet x = 5
(instead of leaving the invalid?
in there). I wanted to compile it tolet x: undefined | typeof 5 = 5
, but sadly this isn't valid TypeScript: