| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
I'm not sure the details of this strategy can actually be made to work.
But, something can.
|
| |
|
|
|
|
|
| |
The comments in WordBreak and SentenceBreak tests get really long, the
provided buffer would be inadequate. So this just provides a sub-
iterator which will strip comments and comment lines, while keeping an
eye on line numbers for any debugging.
|
| |
|
|
|
|
|
| |
Lets me slip these in:
Closes #12
Closes #14
|
| |
|
|
|
|
|
|
|
|
| |
These turned up an excessive amount of allocations in CanonData and
CompatData, which have been reduced to two through the somewhat
squirrely use of 'magic numbers'.
There are now allocation tests for every allocated structure in the
library, and they run to completion in a reasonable amount of time.
So, that's nice.
|
| | |
|
| | |
|
| |
|
|
|
| |
In the process of refactoring the whole library, so that it doesn't
expose anything called "Data" separately from user functionality.
|
| |
|
|
| |
methods were removed, mem.Allocators were added to deinit as arguments.
|
| |
|
|
|
| |
This does the expected thing: returns the next ?Grapheme without
mutation of the iteration state.
|
| | |
|
| |
|
|
| |
issues.
|
| |
|