I like your solution it takes really small amount of time in comparison with string format operation. My solution takes 3-4 times more than yours 🙂 but current one with string format takes 2-3 times more than mine 🙂. String formatting really heavy operation even in this case when we have to format 10 numbers only

Thank you for this feedback, I've been wondering where the sweet spot of documentation is. I've had the idea of explain like no one has any idea what anything does. But it does seem to annoy seasoned developers. I've been playing with the idea of writing comments on blocks of code instead. My level of discernment is not high enough to figure out what doesn't need be said, yet.

Looking at your solution it looks like you just like to add documentation for the sake of documentation, even when it results in illegible code and a ton of duplication/stating what is obvious even to novices. I won't claim the top solution to be best practices, but less is more in this case when the solution can be whittled down to a single standard lib function call.

Super clever absolutly, Best Practices not even close. Where is your documentation.

yes, and also in some case the word sum will be equals but the words are very diferents. I note it after send the response. how i can modify the test cases of the kata ?

no need for last ret

cjk

test case : "abc" and ["bbb"]

非常惊艳的想法

goos: linux
goarch: amd64
pkg: github.com/fight100year/go-ci-test-workflows-template/codewars/parentheses
BenchmarkValid-4         	 3683244	       322 ns/op	      16 B/op	       4 allocs/op
BenchmarkValidFor-4      	60643119	        17.7 ns/op	       0 B/op	       0 allocs/op
BenchmarkValidRegexp-4   	  238974	      5005 ns/op	    4696 B/op	      31 allocs/op

性能比字符串处理差一个数量级

if list is empty

Approved.

Racket translation