Data structure for storing strings
In computer programming, a rope, or cord, is a data structure composed of smaller strings that is used to efficiently store and manipulate longer strings or entire texts. For example, a text editing program may use a rope to represent the text being edited, so that operations such as insertion, deletion, and random access can be done efficiently.
Description.
A rope is a type of binary tree where each leaf (end node) holds a string of manageable size and length (also known as a "weight"), and each node further up the tree holds the sum of the lengths of all the leaves in its left subtree. A node with two children thus divides the whole string into two parts: the left subtree stores the first part of the string, the right subtree stores the second part of the string, and a node's weight is the length of the first part.
For rope operations, the strings stored in nodes are assumed to be constant immutable objects in the typical nondestructive case, allowing for some copy-on-write behavior. Leaf nodes are usually implemented as basic fixed-length strings with a reference count attached for deallocation when no longer needed, although other garbage collection methods can be used as well.
Operations.
In the following definitions, "N" is the length of the rope, that is, the weight of the root node.
 "Definition:" Create a stack "S" and a list "L". Traverse down the left-most spine of the tree until you reach a leaf l', adding each node "n" to "S". Add l' to "L". The parent of l' ("p") is at the top of the stack. Repeat the procedure for p's right subtree.
Collect leaves.
final class InOrderRopeIterator implements Iterator ;RopeLike ; {
 private final Deque ;RopeLike ; stack;
 [Email] RopeLike root) {
 stack = new ArrayDeque ; ;();
 var c = root;
 while (c != null) {
 stack.push(c);
 c = c.getLeft();
 [Tag]
 public boolean hasNext() {
 return stack.size() ; 0;
 [Tag]
 public RopeLike next() {
 val result = stack.pop();
 if (!stack.isEmpty()) {
 var parent = stack.pop();
 var right = parent.getRight();
 if (right != null) {
 stack.push(right);
 var cleft = right.getLeft();
 while (cleft != null) {
 stack.push(cleft);
 cleft = cleft.getLeft();
 return result;
 "Definition:" Collect the set of leaves "L" and rebuild the tree from the bottom-up.
Rebalance.
static boolean isBalanced(RopeLike r) {
 val depth = r.depth();
 if (depth ;= FIBONACCI_SEQUENCE.length - 2) {
 return false;
 return FIBONACCI_SEQUENCE[depth + 2] ;= r.weight();
static RopeLike rebalance(RopeLike r) {
 if (!isBalanced(r)) {
 val leaves = Ropes.collectLeaves(r);
 return merge(leaves, 0, leaves.size());
 return r;
static RopeLike merge(List ;RopeLike ; leaves) {
 return merge(leaves, 0, leaves.size());
static RopeLike merge(List ;RopeLike ; leaves, int start, int end) {
 int range = end - start;
 if (range == 1) {
 return leaves.get(start);
 if (range == 2) {
 return new RopeLikeTree(leaves.get(start), leaves.get(start + 1));
 int mid = start + (range / 2);
 return new RopeLikeTree(merge(leaves, start, mid), merge(leaves, mid, end));
 "Definition:" codice_1: insert the string "S’" beginning at position "i" in the string "s", to form a new string "C"1, ..., "Ci", "S"', "C""i" + 1, ..., "Cm".
 "Time complexity:" &amp;NoBreak;&amp;NoBreak;.
Insert.
This operation can be done by a codice_2 and two codice_3 operations. The cost is the sum of the three.
public Rope insert(int idx, CharSequence sequence) {
 if (idx == 0) {
 return prepend(sequence);
 if (idx == length()) {
 return append(sequence);
 val lhs = base.split(idx);
 return new Rope(Ropes.concat(lhs.fst.append(sequence), lhs.snd));
 "Definition:" codice_4: return the character at position "i"
 "Time complexity:" &amp;NoBreak;&amp;NoBreak;
Index.
To retrieve the "i"-th character, we begin a recursive search from the root node:
[Tag]
public int indexOf(char ch, int startIndex) {
 if (startIndex ; weight) {
 return right.indexOf(ch, startIndex - weight);
 return left.indexOf(ch, startIndex);
For example, to find the character at in Figure 2.1 shown on the right, start at the root node (A), find that 22 is greater than 10 and there is a left child, so go to the left child (B). 9 is less than 10, so subtract 9 from 10 (leaving ) and go to the right child (D). Then because 6 is greater than 1 and there's a left child, go to the left child (G). 2 is greater than 1 and there's a left child, so go to the left child again (J). Finally 2 is greater than 1 but there is no left child, so the character at index 1 of the short string "na" (ie "n") is the answer. (1-based index)
 "Definition:" codice_5: concatenate two ropes, "S"1 and "S"2, into a single rope.
 "Time complexity:" &amp;NoBreak;&amp;NoBreak; (or &amp;NoBreak;&amp;NoBreak; time to compute the root weight)
Concat.
A concatenation can be performed simply by creating a new root node with left = S1 and right = S2, which is constant time. The weight of the parent node is set to the length of the left child "S"1, which would take &amp;NoBreak;&amp;NoBreak; time, if the tree is balanced.
As most rope operations require balanced trees, the tree may need to be re-balanced after concatenation.
 "Definition:" codice_6: split the string "S" into two new strings "S"1 and "S"2, "S"1 = "C"1, ..., "Ci" and "S"2 = "C""i" + 1, ..., "Cm".
 "Time complexity:" &amp;NoBreak;&amp;NoBreak;
Split.
There are two cases that must be dealt with:
The second case reduces to the first by splitting the string at the split point to create two new leaf nodes, then creating a new node that is the parent of the two component strings.
For example, to split the 22-character rope pictured in Figure 2.3 into two equal component ropes of length 11, query the 12th character to locate the node "K" at the bottom level. Remove the link between "K" and "G". Go to the parent of "G" and subtract the weight of "K" from the weight of "D". Travel up the tree and remove any right links to subtrees covering characters past position 11, subtracting the weight of "K" from their parent nodes (only node "D" and "A", in this case). Finally, build up the newly orphaned nodes "K" and "H" by concatenating them together and creating a new parent "P" with weight equal to the length of the left node "K".
As most rope operations require balanced trees, the tree may need to be re-balanced after splitting.
public Pair ;RopeLike, RopeLike ; split(int index) {
 if (index ; weight) {
 val split = left.split(index);
 return Pair.of(rebalance(split.fst), rebalance(new RopeLikeTree(split.snd, right)));
 } else if (index ; weight) {
 val split = right.split(index - weight);
 return Pair.of(rebalance(new RopeLikeTree(left, split.fst)), rebalance(split.snd));
 } else {
 return Pair.of(left, right);
 "Definition:" codice_7: delete the substring "Ci", …, "C""i" + "j" − 1, from "s" to form a new string "C"1, …, "C""i" − 1, "C""i" + "j", …, "Cm".
 "Time complexity:" &amp;NoBreak;&amp;NoBreak;.
Delete.
This operation can be done by two codice_2 and one codice_3 operation. First, split the rope in three, divided by "i"-th and "i+j"-th character respectively, which extracts the string to delete in a separate node. Then concatenate the other two nodes.
[Tag]
public RopeLike delete(int start, int length) {
 val lhs = split(start);
 val rhs = split(start + length);
 return rebalance(new RopeLikeTree(lhs.fst, rhs.snd));
 "Definition:" codice_10: output the string "Ci", …, "C""i" + "j" − 1.
 "Time complexity:" &amp;NoBreak;&amp;NoBreak;
Report.
To report the string "Ci", …, "C""i" + "j" − 1, find the node "u" that contains "Ci" and , and then traverse "T" starting at node "u". Output "Ci", …, "C""i" + "j" − 1 by doing an in-order traversal of "T" starting at node "u".
Comparison with monolithic arrays.
Advantages:
Disadvantages:
This table compares the "algorithmic" traits of string and rope implementations, not their "raw speed". Array-based strings have smaller overhead, so (for example) concatenation and split operations are faster on small datasets. However, when array-based strings are used for longer strings, time complexity and memory use for inserting and deleting characters becomes unacceptably large. In contrast, a rope data structure has stable performance regardless of data size. Further, the space complexity for ropes and arrays are both O(n). In summary, ropes are preferable when the data is large and modified often.
References.
 ;templatestyles src="Reflist/styles.css" / ;