Very good remark, but everything is not so easy and depends entirely on data.
You can test it yourself, just imagine the list with 10 distinct values, each repeated 1000 times. It's much more easy to 'hashset' it in the start, then sort 10 values, then sorted 10000 values, and only then take only unique ones.
So, one more time, it depends on the data.

I don't quite understand why but I had the same problem. I would get a 159.0 when I printed it but as I cast it into Int it changed to 158. Not sure why but it happened I had to come up with a fix

Thank you

can you try again please?

agree, what's the point of fugly code. One-liner, ok, I get it, but writing java.util.stream.Stream on the line that is already long is just pure fcuk up

While that is ugly that's an opinion, not an issue.

Closing.

I mean, this kata isn't really meant to be testing your ability to write idiomatic Java; quite the opposite, in fact.

OK, the updated translations have been approved. @shadowmanos, please let us know if your issue has been resolved.

@shadowmanos Sorry for the mistake. I've modified the tests. All you have to do is copy your solution, click reset, and paste your solution, and re-submit.

Wait, I mentioned that I didn't do the isSubsequence. Let me finish this.

I've fixed this issue in this fork. Please approve and mark this issue as resolved.

I can't edit it can republish. I've tried many many times and its just timeout.

Ice, did you notice the JavaScript and Haskell tests are not testing for equality of the user solution and some reference solution, but are testing the solution is valid in terms of length and being a subsequence of both inputs? Did you implement this in your translations?