rivo
@dchapes I was wondering if I had missed something but looking into #10 and #11, I see that I'm currently waiting for your input. For #10, no PR has been...
I'm wondering why you would use this package if you only deal with printable ASCII characters.
I currently don't have time to look into GitHub Actions. Unless there's a specific need for it (in which case, please elaborate), this is going to be on the backburner.
Which Go version are you using? Does this happen with Go 1.18, too?
Please upgrade to Go 1.18, the current version since March 2022. This package requires v1.18 for various reasons.
I'll write this here as there is no issue to go along with the PR's you submitted and I'd like to note a few general things: - First of all,...
I should also note that if you want to keep working on this PR after the changes mentioned above, it should be broken into multiple PR's so we can discuss/approve...
Do you have an actual use case in your application where you work with slices of runes?
I'm simplifying as I go along. This engine has probably been rewritten three or four times already. The biggest driver of these changes was proper Unicode support. I have to...
What's the number of the 3-liner fix?