✨ Add message equivalence #588
Merged
Conversation
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
elbeno
force-pushed
the
message-equivalence
branch
3 times, most recently
from
9bb7cd6 to
bb75357
Compare
Problem: - equality is not defined for span, so it is also not defined for messages. Solution: - add `msg::equivalent` to determine whether two message instances are equivalent (all fields have the same values). - equivalence is defined for all combinations of owning, const and mutable view types.
elbeno
force-pushed
the
message-equivalence
branch
from
bb75357 to
6659e8d
Compare
mjcaisse-intel
approved these changes
Aug 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Problem:
Solution:
msg::equivalentto determine whether two message instances areequivalent (all fields have the same values).
types.