Caveats: Add Avoid Type Assertions section #188
Closed
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.
Ternary expression optimization relays on "correct" types.
TypeScript language allows Type Assertions to be used, which allows "incorrect" typing when the developer find it suitable.
Usually you could find Type Assertions used in small code pieces where a the developer "known what they are doing" and the developer write the code that can handle the "correct" run-time type.
The problem is that due to Ternary Optimization, the transpiled LUA code will NOT behave as the developer expects, even if they write the code while considering the "correct" type !
Related to this Issue