Well I call it Best Practices.

Rejected:

Current C version already had random tests with wider fixed test coverage and using latest version (same goes to the description)

thanks for your reply, I will leave the name as is, changing the writing style does not affect performance

I did not tell you that it was better. You asked for a workaround and I gave you one. You can choose whichever option you like. I don't think it matters too much that the name is the same as the builtin, since 1) you can still use the builtin in your solution without any change and 2) this function will only ever be used for this kata, it's not going to be part of a large project where it could indeed confuse readers. If you insist on not using the same name, at least do not use PascalCase for it, as the link above specifically discourages this style for function names.

Hi can you tell me why it is better to use the name of the built-in function than to change the writing style?

you can do this:

import "package:solution/solution.dart" as solution;

void main() {
  group("Fixed Tests", () {
    test("Test str:hello world!,  prfx:hello", () {
      expect(solution.startsWith("hello world!", "hello"), equals(true));
    });

it's better than using PascalCase for the function's name, as the official Dart style guide discourages this

We need more Python tests because
if prefix > st: return False
covers all tests for
len(prefix) > len(st).

fixed

trashy_incel's fork got approved

Resolved for C

the fork in question

I approved the fork, but in the meantime another user has been working on their fork addressing the same issues, but since they did not publish it, it was not visible. When they publish their fork we'd have to check it and see if it has any further improvements, and eventually approve it.

done in this fork

C fork

• making description language-agnotic (fixing this issue)
• adding random tests (fixing this issue
• using booleans as return type instead of int

Sorry I didn't notice your replies earlier. I'm not sure what's the correct way to do this, but hopefully I'll find some time in near future to figure it out.