Support deserialization of YAML anchors of value types #16186
+25
−15
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.
Resolves #13830. All objects are now boxed so that they can be stored into the parse context uniformly.
This does not affect how the GC sees
YAML::ParseContext#@anchors
; since the hash's key type isString
,Hash::Entry(String, T)
is always non-atomic, thus the switch fromUInt64
toVoid*
makes no differences. (In factVoid*
is probably more correct here.)YAML.parse
already handles anchors regardless of their types, since they are allYAML::Any
s;YAML::Nodes.parse
returns a document and never resolves aliases. These methods are not affected in this patch.