| Age | Commit message (Collapse) | Author |
|---|
|
It shall not be used by Config_tree, so there is no reason to keep it there.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Situations when two lists are the same and when they don't have a common
part become indistinguishable, but that's rarely needed.
|
|
input from the reference tree anyway.
Make value modification functions behaviour multi-value node aware.
|
|
|
|
That was not so much of a bad idea after all.
|
|
|
|
This is important for decision is set should add or replace a value.
|
|
Mainly for quickly getting data from a reference tree.
|
|
Make insertion at the beginning default behaviour.
Implement insertion at the end.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(i.e. no constraints means anything goes).
|
|
|
|
test.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
constraintErrorMessage.
|
|
|
|
where one contains another (starting with the first element).
|
|
|
|
a tree.
|
|
Making it linear time at cost of knowing the data for all path elements
was probably a bad idea.
|
|
It now lives in a Util, a module that implements the adopter design pattern.
|
|
Looks like it was a bad idea.
This reverts commit 7c02dc2a949798a3fea3dbcce5a63888a3f10f51.
|
|
|
|
Rename helpString to just help.
|
