Pass the emit_context by (non-const) reference#7
Merged
BurningEnlightenment merged 1 commit intomasterfrom Feb 3, 2023
Merged
Conversation
In order to allow storing state in the emit_context in a future API extension it needs to be mutable. Note that since it stores the output_buffer by reference, there are no concerns w.r.t. codecs replacing the current output_buffer. BREAKING CHANGE: The `(de|en)code()` APIs won't accept an `emit_context const &` argument anymore
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
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.
Purpose
In order to allow storing state in the emit_context in a future API extension it needs to be mutable. Note that since it stores the output_buffer by reference, there are no concerns w.r.t. codecs replacing the current output_buffer.
Additional explanatory comments
This was an early design mishap in #4 which I forgot to rectify before merging.