that was somethig like explain me why 2+2 = 5

ni hasta goku hizo este nivel de dedicacion! XD

Mucho codigo para algo tan simple V;, todo bien en casa bro?

(C#) The description makes no mention of handling null values, yet "Test Empty" in the hidden test cases tests with a null value.
It's also unclear what "Text Exception" is testing, or what it's passing. It seems to expect false when my otherwise-valid solution returns true.
The only valid case in C# for an IEnumerator to throw an exception is if the underlying collection is modified during iteration. Strings are immutable so this is an unreachable scenario.

Thanks, I was struggling on this one :)

the preloaded section emits warnings to STDERR:

Note: src/main/java/ClassHelper.java uses unchecked or unsafe operations.

This seems to be caused by this line:

class SpecialFileManager extends ForwardingJavaFileManager {

ForwardingJavaFileManager is a generic class:

Class ForwardingJavaFileManager<M extends JavaFileManager>

so the subclass SpecialFileManager is a raw type, hence the warnings. It should either be parameterized itself, or should extend a parameterized version of ForwardingJavaFileManager.

This is just beautiful

Java

I enjoyed this kata since I'm a big fan of regular expressions, But it's more suited at 5kyu instead of 4.

That was fun :-)

Ruby version kumited, please check and comment or approve.

Which language did you solve in?

There is a strange requirement: "true123 is an identifier, as opposed to boolean followed by integer".. Looks like foreign for this task. Actually I ignored it (did not check and maintain this case). And my solvation passed all tests! May be you should remove this requirement from kata description?

Oh, you are right.

... yielding Token items until there are no more items to yield, at which point it should do whatever the appropriate action is for your chosen language.

I don't know Java, but a quick search reveals that next() should throw an exception when there's nothing more to return. Since this is the official spec of the interface, I'd say it's rather more obvious than not.