Tell payloads and encoders how much space they have to work with #4876
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.
This change allows payload and encoder modules to become much more dynamic by providing an
available_space
accessor that is set by theEncodedPayload
wrapper. As it stands today, this does nothing, but it opens the door for evasive encoders and payloads that can enable features and randomization based on available room. The actual payloads that use this are being implemented in the complex payload branch.