Fix assert failure in await expression with non-null assertion#24
Draft
Fix assert failure in await expression with non-null assertion#24
Conversation
...including mandatory workflow, time constraints, and best practices.
...including mandatory tasks, debugging tips, and common commands.
...to the copilot instructions for better guidance.
...including how to give up, common commands, session finishing tasks, debugging tips, compiler tests, and fourslash testing.
Co-authored-by: RyanCavanaugh <6685088+RyanCavanaugh@users.noreply.github.com>
Co-authored-by: RyanCavanaugh <6685088+RyanCavanaugh@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Assert failure in await expression
Fix assert failure in await expression with non-null assertion
Jul 15, 2025
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
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 fixes a debug assertion failure that occurs when using
NODE_ENV=developmentwith await expressions followed by non-null assertions.Issue
The following code would cause a debug assertion failure when compiled with
NODE_ENV=development:The error was:
Root Cause
In
src/compiler/transformers/ts.ts, thevisitNonNullExpressionfunction was incorrectly usingisLeftHandSideExpressionas the test when visiting the inner expression:The issue is that await expressions are unary expressions, not left-hand side expressions, so the debug assertion would fail when
NODE_ENV=developmentenabled debug checks.Solution
Changed the visitor test from
isLeftHandSideExpressiontoisExpressionto match the pattern used by similar transformation functions likevisitAssertionExpressionandvisitSatisfiesExpression:Testing
awaitNonNullAssertion.tscovering various await + non-null assertion patternsFixes #23.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.