-
Notifications
You must be signed in to change notification settings - Fork 0
More fixes #29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
More fixes #29
Conversation
This reverts commit 1c49397.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking pretty good! Just minor suggestions mostly.
Big thing is the binary search vs. linear progression for character splitting. Maybe I'm missing something? Let's chat if there's an optimization and whether to do it here or in follow on work
Thanks sir! I'll add the character explicit split. The binary search thing
is a bit esoteric to me as well, honestly.
…On Tue, Jul 15, 2025, 7:14 PM Ryan Roemer ***@***.***> wrote:
***@***.**** commented on this pull request.
This is looking pretty good! Just minor suggestions mostly.
Big thing is the binary search vs. linear progression for character
splitting. Maybe I'm missing something? Let's chat if there's an
optimization and whether to do it here or in follow on work
—
Reply to this email directly, view it on GitHub
<#29 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE7IYMLJF7N7SUACHJNBXOL3IWYOZAVCNFSM6AAAAACBSRLQXOVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTAMRSHA4DIMRVGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
As discussed with @mscottx88, we're still waiting for a round of reviews on this and a bit of discussion. |
Closes #28