Closed mipearson closed 9 years ago
Ok, so Terminal 2.0.0 has been released, which no longer does the encoding or emoji munging. We're good to switch to using this super-powered Golang version. Now… do we just use this repo or start a fresh one for the golang version?
Can you tell me why you dropped the encoding stuff and/or how you dropped it? Worried that I'll need to change my impl.
I've just put the onus onto the invoker to ensure they're passing in UTF-8. If you have your locale set incorrectly, then it'll bork. I don't think you need to do anything on the go side.
For context, if you pass in a wrongly-encoded UTF-8 string to the Ruby gem it throws an error in the regex gear. Not something you need to do I presume.
WFM!
Letting Ruby handle Emoji for now. This imparts an approximately 2x performance penalty on large sets .. but it's still miles ahead of the Ruby impl. Original acceptance tests have been ported from Ruby to Go, and I've added a couple of additional ones for correctness of multibyte handling.
Benches: