Skip to content

fix: detection of non-unique message opcodes #493

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom
Merged
merged 2 commits into from
Jun 26, 2024
Merged

fix: detection of non-unique message opcodes #493

merged 2 commits into from
Jun 26, 2024
+247 −34

Conversation

anton-trunov
Copy link
Member

Closes #482

  • I have updated CHANGELOG.md
  • [ ] I have documented my contribution in Tact Docs: https://github.com/tact-lang/tact-docs/pulls/PR_NUMBER
  • I have added tests to demonstrate the contribution is correctly implemented: this usually includes both positive and negative tests, showing the happy path(s) and featuring intentionally broken cases
  • I have run all the tests locally and no test failure was reported
  • I have run the linter, formatter and spellchecker
  • I did not do unrelated and/or undiscussed refactorings

@anton-trunov anton-trunov added this to the v1.4.1 milestone Jun 26, 2024
@anton-trunov anton-trunov self-assigned this Jun 26, 2024
@anton-trunov anton-trunov merged commit 17efa18 into main Jun 26, 2024
3 checks passed
@anton-trunov anton-trunov deleted the fix-message-opcode-non-detected-clashes branch June 26, 2024 18:56
# for free to join this conversation on GitHub. Already have an account? # to comment
Reviewers
No reviews
Assignees

@anton-trunov anton-trunov

Labels
None yet
Projects
None yet
Milestone
v1.4.1
Development

Successfully merging this pull request may close these issues.

Messages with the same opcodes are not detected
1 participant
@anton-trunov