You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should be the first step to making D:YAML Nodes range based. Also, when this is added, the current opApply() should be deprecated (but kept for one/more releases).
E.g. sequence, mapping, mappingKeys, mappingValues. These will assert that the key is a sequence/mapping.
Range primitives of these ranges could be more @safe/pure/nothrow/@nogc than current monolithic opApply().
Future ranges could also include depth/breadth first range over all Nodes and their subnodes. The element of such ranges should include Node packed with current depth and maybe some more info.
The text was updated successfully, but these errors were encountered:
Should be the first step to making D:YAML Nodes range based. Also, when this is added, the current opApply() should be deprecated (but kept for one/more releases).
E.g.
sequence
,mapping
,mappingKeys
,mappingValues
. These will assert that the key is a sequence/mapping.Example:
string[] strings = node.mappingKeys.map!(n => n.as!string).array;
Range primitives of these ranges could be more
@safe
/pure
/nothrow
/@nogc
than current monolithicopApply()
.Future ranges could also include depth/breadth first range over all Nodes and their subnodes. The element of such ranges should include Node packed with current depth and maybe some more info.
The text was updated successfully, but these errors were encountered: