Lines Matching refs:rope

161         a rope - and thus couldn't except - it would be hard to prove this).
1860         a rope for the resulting replacement.
1871         We use this to do a substring find without having to resolve the rope.
1897         (JSC::stringProtoFuncReplace): Don't resolve a rope unless we need to. Do
1898         use our new replaceCharacter function if possible. Do use a rope to
5909         Calling getIndex() on a JSString in rope form may result in a JSException being thrown
7628         JSString::getIndex() calls value() to resolve the string value (is a rope)
7634         Simple fix is to be able to get an index from a rope without resolving to
7837         to ensure that the rope's fibers are also destroyed.
7846         A rope is a recursive data structure where each node in the rope holds a set of
7848         another rope node.  A low bit in each pointer is used to distinguish between
7849         rope & string elements, in a fashion similar to the recently-removed
7859         This allows us to change the rope's fibers to interrogate the object rather
7968         (JSC::Rope::Fiber::rope):
13263         (rather than externally allocating an object to hold the rope).
13853 …  Add a rope representation to JSString.  Presently JSString always holds its data in UString form.
13855 …variable sized, reference-counted rope node retaining a set of UString::Reps (or other rope nopes).
13858 …   but by holding the string in a rope representation during construction we can avoid copying data
13882               in rope representation, produces a rope as a result.
13898         (JSC::JSString::Rope::Fiber::rope):
13911         (JSC::JSString::rope):
13919             - Add rope form.