Function signature is def bestWord(points: Vector[Char], words: Vector[String]): Int = ??? but should be def bestWord(points: Vector[Int], words: Vector[String]): Int = ???.

That's your point of view. Some could say it's to find an easy to maintain production-like piece of code. Others may want to play code golf and find the shortest possible solution. Others to find the most efficient one.

Depends on your context.

Hey @KayleighWasTaken , we should probably edit the description for the Scala language to specify that we should return empty strings rather than false when the resulting string is empty or longer than 140 chars.

The Scala translation doesn't provide a correct function signature in the solution set-up:

It should be: def moveZeroes(lst: List[Int]): List[Int] = ???

I guess you're assuming requirements that don't exist then!

In the Scala version, import org.scalatest.flatspec.AnyFlatSpec is missing in sample cases. (@KayleighWasTaken)

Wait, what?

Scala translation's solution setup return type is List[Double], but the solution is expected to return (Double, Double)

Hum, translation was approved and Kata was available in Scala for an hour or so, but I can't see it no more! Not sure what happened here.

Hum, why Number as a return type? It's rarely used in Scala and it doesn't bring much to the Kata, specially with input types being Ints.

And it would make any solution using .toDouble in the division fail during the submit but not with sample test cases.

I'd suggest using Double as a return type.

I think there's a merge conflict with the description