| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This reduces collisions by 11% while adding no branching, so I'm calling
it a win.
|
| | |
|
| | |
|
| |\
| |
| |
| | |
Thanks again, Jacob!
|
| | |\ |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
CanonData included. I may still sort out caseless matching without
allocation, but that's a stretch goal.
Closes #86
Closes #85
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
After coping with a spuriously broken autohash for awhile, I got the
one remaining hash table moved into memory, so there's no further
reason to put up with allocation of basic structures.
So that's nice.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This gets us up to feature parity with Jacob's work. I want to
eliminate that last allocation using the comptime hash map, and then
see about eliminating allocations from case comparisons as well.
That should just about do it.
|
| | | |
| | |
| | |
| | | |
Both of which deserve some further attention.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
And DisplayWidth, although untested at present.
The plan is to just work through the codegen / module pairings, and
move tests over until everything is covered.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
`DisplayWidth.graphemeClusterWidth` function' (#81) from lch361/zg:graphemeClusterWidth into master
Reviewed-on: https://codeberg.org/atman/zg/pulls/81
|
| | |\ \ \
| |/ / /
|/| | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
wide-diverse-emoji into master
Reviewed-on: https://codeberg.org/atman/zg/pulls/96
|
| |/ / / /
| | | |
| | | |
| | | | |
Fix: #82
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Close #90
Close #87
Close #83
Thanks everyone.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
easier packaging
|
| | | | |
| | | |
| | | |
| | | | |
Removes compression support
|
| |/ / / |
|
| |/ / |
|
| |\ \
| |/
|/| |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
That completes the set. I do think it's possible to bum a few more
cycles from the implementation, but, I'm not going to. It passes
the acceptance suite and that's what it needs to do.
|
| | | |
|
| | |
| |
| |
| |
| | |
Hopefully I can talk users out of taking advantage of this configuration
but I'll have better luck with that if it's available.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These create reverse or forward iterators before or after a Word. So
this way, the user can get the word at an index, then iterate forward
or back from that word.
Also:
Fixes #59
Which was fixed awhile back, but I don't feel like doing repo surgery
to tag the fix where it happened. We have blame for that kind of
thing.
|
| | |
| |
| |
| |
| | |
`ziglyph` is no longer maintained and basically abandoned, there's no
need to keep the comparison between them active going forward.
|
| | |
| |
| |
| | |
Rebasing my way through that again was just not in the cards.
|
| | |
| |
| |
| |
| |
| | |
In keeping with the new nomenclature, we're calling the module "Words",
not "WordBreak". The latter is Unicode jargon, the module provides word
iterators. Words are the figure, word breaks are the ground.
|
| | | |
|
| | | |
|
| | | |
|
| | |\ |
|
| | | |\ |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
Closes #53
|
| | | |/ |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I removed the initAtIndex functions from the public vocabulary, because
the last couple of days of sweat and blood prove that it's hard to use
correctly.
That's probably it for WordBreak, now to fix the overlong bug on v0.14
and get this integrated with the new reverse grapheme iterator.
|