Make it easier to create a Value from owned or erased external types #339
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 PR allows consumers to work around
Value
's required lifetime constraints in two ways:Primitive
type is all about.Fill
andSlot
types are all about.The
Fill
API is a more advanced initialization strategy (it's actually a kind of visitor that just tries very hard to look like initialization), so it isn't exported from thelog::kv
module. Instead, this PR makes thevalue
module public and leavesFill
andSlot
in there. We need something like this to be able to translate a&'kvs dyn tracing::Value
into alog::kv::Value<'kvs>
.