Partial extended multiplexing support#109
Merged
Adhara3 merged 2 commits intoEFeru:mainfrom Jan 9, 2026
Merged
Conversation
Owner
|
Hi @Uight thanks for your contribuition. From my side it looks good. |
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
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.
A partial implementation for extended multiplexing support.
It basically allows the parser to parse the lines and checks for correct syntax and delivers the data to the builder.
But in the builder nothing is done to the data. This is so the files with extended multiplexing can be parsed;
Due to all the discussions in earlier implementations of this i decided to try to implement it in smaller parts.
This part in particular shouldnt be controversial at all and just be mergable.
But then the question still remains how to truly handle the extended multiplexing data.