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
Improvement: avoid building RotatedTextWithTerminator and have VirtuallyRotatedTextWithTerminator access directly to the underlying TextWithTerminator.
Currently the construction of a VirtuallyRotatedTextWithTerminator instance requires wrapping the underlying TextWithTerminator into a RotatedTextWithTerminator: c.p. the following excerpt from
Why: on large input (strings of hundreds of MB), a RotatedTextWithTerminator instance has to be built for each "virtual rotation" of the input, i.e. as many instances of this object are created as chars in the input. This leads to a high memory usage, and possibly to OutOfMemoryException.
The text was updated successfully, but these errors were encountered:
Improvement: avoid building
RotatedTextWithTerminator
and haveVirtuallyRotatedTextWithTerminator
access directly to the underlyingTextWithTerminator
.Currently the construction of a
VirtuallyRotatedTextWithTerminator
instance requires wrapping the underlyingTextWithTerminator
into aRotatedTextWithTerminator
: c.p. the following excerpt fromMoreStructures/MoreStructures/TextWithTerminatorExtensions.cs
Line 40 in 0365e3b
Why: on large input (strings of hundreds of MB), a
RotatedTextWithTerminator
instance has to be built for each "virtual rotation" of the input, i.e. as many instances of this object are created as chars in the input. This leads to a high memory usage, and possibly toOutOfMemoryException
.The text was updated successfully, but these errors were encountered: