Use MaybeUninit
to avoid aliasing Vec
and String
while they can be moved.
#30
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.
The idea is: by storing the wrapped
Template
held byTemplateBuf
inMaybeUninit
, we're not really storing a reference to the source data. Or at-least not as far as the compiler is aware.Instead, we "recreate" the
Template
with reference to the source data when we useMaybeUninit::assume_init_ref()
.I'm not 100% sure this is totally sound, but
miri
accepts it. The PR also addscargo miri test
to the CI workflow.The PR also switches to
Pin<String>
andPin<Vec<u8>>
, although that currently doesn't actually do anything about aliasing rules.Pin
may have different aliasing rules in the future, which will likely be more appropriate.