Conversation
samalws-tob
force-pushed
the
feat/assert-codes
branch
from
cf6867e to
feca432
Compare
Contributor
Author
|
yeah I think this is good. in theory we could spam more tests to cover every possible case, not sure if that's really necessary |
Collaborator
|
I don't think |
Contributor
Author
|
yep youre right. needs cleanup work but pretty sure it's functional and the tests run now |
samalws-tob
force-pushed
the
feat/assert-codes
branch
from
468eb39 to
a65310e
Compare
Contributor
Author
|
aight should be better now |
anishnaik
approved these changes
Mar 6, 2026
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
2 participants
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.
VIBE CODED. I think this is correct, just need to double check
resolves #501
adds a bunch of assert* cheatcodes