All characters considered as vowel are currently listed in the description (y/Y are not listed as vowels)

Hours later; I added fixed test that your first (?) solution doesn't pass anymore. Thanks for your post.

There is a small flaw (or typo) in your code; the 200 random tests don't catch it every time so yes by mashing the submit button it happens you pass. When your code fails it is with long arrays of long strings and I can't put these long tests in fixed tests; until now I was not able to reproduce the same things with a short test. Sorry...

Description, C++ and C# tests adjusted.

All translations use chars in range [32; 127] (126 in Ruby). This "rule", which is not even a rule, should be dropped, and, preferably, C++ and C# tests should be adjusted to use the same range as other languages instead of having ~30 unprintable chars.

( JS, possibly others )

• The input message consists of ASCII characters between 0 and 100 (7-bit)

Test messages actually consist of ASCII characters between 32 and 127.

Adjusting the description is the better option probably.

Thanks. I was unsure if this rule also applied to output of my send function;

Please look at the first rule again.

Hi during the tests im getting following error

Expected: equal to 00 0 0 0 00 00 0 0 00 0 0 0
Actual: 0 0 00 00 0 0 00 0 0 0

for % ascii cnumber is 37
It's binary pepresentation is then 100101, and example suggests 0100101

Hi. For some languages 'y' is also concidered a vovel. I know this isn't the case for English, but it would be great to highlight it in Kata description, or even test examples. It would spare some confusion for foreigners like me.

That means you have error (my money is reffering to not allocated memory) somewhere in your code, and your function returned no input.

I tried to debug your code. In the first fixed test of "Sample Tests", I got:

Fixed_Tests
 Log
Actual: {103, 101}
Error testing StepInPrimes::step(2, 100, 110)!
Expected: {101, 103}
Actual: {103, 101}

or for another one:

Fixed_Tests
 Log
Actual: {5, 3}
Error testing StepInPrimes::step(2, 2, 50)!
Expected: {3, 5}
Actual: {5, 3}

It seems (at least...) that your return is always in wrong order... Try first to correct that.

Sorry about that, the testing framework doesn't know how to print pairs so when the solution fails it reports " [unsupported type]". This issue was already showing (maybe you can see it some posts below). The only way is to have a code that doesnt't fail:-(
Maybe you could print yourself the input and your output. Example for output:

std::string output_pair(std::pair<long long, long long> p) {
  return "{" + to_string(p.first) + ", " + to_string(p.second) + "}";
}

Hope that helps!