A valid time with a trailing newline (e.g. '12:30:00\n') should be added as a fixed test. Many solutions use regex patterns like /^([0-1]\d|2[0-3])(:[0-5]\d){2}$/, but the '$' token matches on different things depending on language, notably Python and Java, which will match the position before a terminal newline as well as the end of the string. Also, annoyingly, just replacing the '$' with '\Z' isn't always effective, as in Python, '\Z' matches only the end of the string, while in Java it's just a synonym for '$'.

Java translation!

After doing so many Python Kata and learning from one-liner solutions, I'm happy that I can now have one-liner solutions equivalent to these :D

No worries - I was just a little grumpy and should have walked away, calmed down and not posted and hence troubled you. Figuring out the solution once I realised what was expected was really simple, perhaps so simple being the reason I assumed the intent was to get us to create the classes, structs ow whatever we chose to be appropiate. Since solved.

You do not need to create them, they are already available in preloaded sinppet as:

struct Point{
  double x;
  double y;
};

struct Triangle{
  Point a;
  Point b;
  Point c;
};

There is a sentence in the description which attempts to explain this, but yeah, mignt be not clear enough. You do not need to define anything, or include anything, you just use the existing classes.

I created my own Point and Triangle classes in C++ and approriate class member functions then when I run the test I get an error: "Redefinition of Point, Triangle ... Point preveiously defined here." How do I get to see these existing definitions for Point and Triangle?

Thats just amazing

Lmao🤣🤣🤣🤣🤣

Hi I don't know why the test got failed in the first test and passed in the second although they are the same amount $1.23.

I need help please

"\nX" already included in the Ruby tests.

Should include it for the other languages as well, for consistency.

Ruby random tests added in this fork

Done for Ruby, in this fork

They may be well aware of that but they still might not be aware that they did that, and then didn't fully understand the situation described by the error message and seeing how that relates to their function's behaviour and what's in the test code, which they may not have looked at. They're also not posting the full error message here and .. and their current solution misinterprets how rounding is applied here. But that's just what it's like when everything is new isn't it. Nothing gets enough attention when everything demands attention. Not particularly strange.

How did you solve like 20 other kata without knowing that you're supposed to return the answer and not print it?