Advanced multiplexing #167
Open
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
Ext3h
commented
Jul 30, 2025
Ext3h
commented
Jul 30, 2025
Ext3h
commented
Jul 30, 2025
Ext3h
force-pushed
the
advanced_multiplexing
branch
from
48a57ee to
73741f7
Compare
Ext3h
commented
Jul 30, 2025
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.
Resolves #84, eliminates costly heap-allocated binder objects and generally ensures compatibility with C++ named requirements for containers and iterators.
Resolves #166 - specifically correcting the serialization / deserialization of
multiplexer_indicator, and adding validation for the the edge cases you can run into when not knowing the difference between simple and "advanced" multiplexing in DBC.No externally visible ABI (at least not on exported symbols for shared library) or API changes,