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
What opt_each currently handles is a situation where we can have each of these two options:
key: "a single value"
or
key:
- "a first value"
- "a second value"
- "and some more..."
This would be better named one_or_each.
On the other hand, we miss a function to handle the case where we look for 0 or more values, that is, where the key might be completely missing.
This could maybe be written like that:
// for a listeach(tree, or_none, [](PC_tree_t value) {
}
// for a mappingeach(tree, or_none, [](PC_tree_t key, PC_tree_t value) {
}
that way, the variant could be easily added to all functions.
The text was updated successfully, but these errors were encountered:
What
opt_each
currently handles is a situation where we can have each of these two options:or
This would be better named
one_or_each
.On the other hand, we miss a function to handle the case where we look for 0 or more values, that is, where the key might be completely missing.
This could maybe be written like that:
that way, the variant could be easily added to all functions.
The text was updated successfully, but these errors were encountered: