refactor(linter/plugins): add debugAssert function#15969
Merged
graphite-app[bot] merged 1 commit intomainfrom Nov 22, 2025
Merged
refactor(linter/plugins): add debugAssert function#15969graphite-app[bot] merged 1 commit intomainfrom
debugAssert function#15969graphite-app[bot] merged 1 commit intomainfrom
Conversation
github-actions
bot
added
A-linter
Member
Author
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
github-actions
bot
added
the
C-cleanup
overlookmotel
force-pushed
the
11-22-refactor_linter_plugins_add_debugassert_function
branch
from
b75558a to
8334f46
Compare
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
Member
Author
Merge activity
|
Add a `debugAssert` function, which works the same as `debug_assert!` in Rust. We can use this to add more assertions to rest of code. Same as `debugAssertIsNonNull` and `typeAssertIs`, this function will be removed entirely in release build - it only performs the check in debug build (which is used in the tests).
graphite-app
bot
force-pushed
the
11-22-refactor_linter_plugins_rename_assertion_functions
branch
from
fa9143e to
ae13704
Compare
graphite-app
bot
force-pushed
the
11-22-refactor_linter_plugins_add_debugassert_function
branch
from
8334f46 to
0a6a288
Compare
Base automatically changed from
11-22-refactor_linter_plugins_rename_assertion_functions
to
main
November 22, 2025 16:00
graphite-app
bot
deleted the
11-22-refactor_linter_plugins_add_debugassert_function
branch
taearls
pushed a commit
to taearls/oxc
that referenced
this pull request
Dec 11, 2025
Add a `debugAssert` function, which works the same as `debug_assert!` in Rust. We can use this to add more assertions to rest of code. Same as `debugAssertIsNonNull` and `typeAssertIs`, this function will be removed entirely in release build - it only performs the check in debug build (which is used in the tests).
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
1 participant
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.
Add a
debugAssertfunction, which works the same asdebug_assert!in Rust. We can use this to add more assertions to rest of code.Same as
debugAssertIsNonNullandtypeAssertIs, this function will be removed entirely in release build - it only performs the check in debug build (which is used in the tests).