Thanks for the spotlight, I've updated the kata.

I did not found any issues atm.

I thought I've already did the update on those typos, sorry.

Nevermind, now I'm failing because it's longer than 6s. =/

I still can't think of another approach. I've seen some weird stuff on internet but I couldn't figure it out.
Anyway, I'll try another time.

Can you tell which is the time threshold for the process?

Because I'm failling from 680ms to 3168ms for process complete.

I'm using ruby, iterative approach with an array.

Didn't got it

Great Kata, but I guess that if you turn off the #scan method and related methods, it would be more funny to solve this problem.

(=

Anyone got this error:

-e:39: [BUG] Segmentation fault at 0x007fff34e28ff8 ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-linux-gnu]
-- Control frame information -----------------------------------------------
c:6727 p:---- s:13479 e:003478 CFUNC :inspect

(...)

(...)

[NOTE] You may have encountered a bug in the Ruby interpreter or extension libraries. Bug reports are welcome. For details: http://www.ruby-lang.org/bugreport.html

I've updated the description to include mentions of nil and empty cases. Thank you for the feedback!

On description:
change('a **& Z') => '1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1' <= 26 characters
On test cases:
Test.assert_equals(change("Ab"), "1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0") <= 25 characters

I'm just telling that the test case that comes with the Kata needs to be fixed.

The test says "it should return 11 followed by 24 zeros" but at the asssertion it's missing one zero. It got me confused :S

I guess the method name was misspeled at the editor. It was written as 'palidrome'.

Lastly, it is a nice challenge!