The best way! I keep forgetting that I don't need to explicity write true and false because the comparison operator always does that automatically for me.

either it was fixed at some point, or the report was wrong. C# sample tests are fine

your string is never nul-terminated because the line-ending logic has precedence over the nul-terminating logic in your if/else

dont use strcat() on uninitialized memory (e.g. that returned by malloc())

in R you want to require "\n" and not "\n" as the line separator if the aim is to create shapes in formatted strings:

cat("aaa\nbbb")

aaa

bbb

cat("aaa\\nbbb")

aaa\nbbb

You should probably mention the language you're talking about. If it was Rust, then it was fixed.

Read this: https://docs.codewars.com/training/troubleshooting#expected-the-same

Not a kata issue.

O meu acontecia exatamente a mesma coisa, só que em Python

Approved

Fixed now then.

Approved.

The comments in the random tests are really not necessary. The code is self-documenting; the comments just distract there.

Please suppress the urge to code golf your test suite. join`` is just less readable than join("") - don't do it, write for readability and maintainability, CW can spare those couple of characters.

I would have commented this directly on the translation, but CW would not let me. It also shows two comments it isn;t actually showing. Something's very wrong there.

Addressed in my current JS fork.

Fork of the JS version to address the open issue regarding random tests and to get it consistent with the current Python version. More fixed tests have also been added for the user's convenience. Now uses Chai and Node v18.