You're right the instructions are unclear due to extra verbosity (and a not-normal use of 'same', math specific maybe?), but what you have provided isn't the same as what the kata asks.

"Create a function that takes two arrays of integers, comp(a, b) [compSame(a, b) in Clojure], and checks if the values in array b are the squares of the values in array 'a' such that there is one value in 'b' for each value in 'a' and no unpaired values. Please be careful since this function can also accept null values for parameters, and negative numbers also have sqares."

This is what it should be, though some of the syntax stuff at the end of the original prompt still applies. The original, while highly specific, really doesn't do the best job of explaining the challenge.

The prompt is unclear and way too verbose. It can really be described in one or two sentences, not the wall of text that it is:

Create a function comp(a, b) [compSame(a, b) in Clojure] that checks if the values in array a are each of the square roots of the values in array b (or vice-versa). Please be careful since this function can also accept null values for parameters, and negative numbers are also square roots.

The way it is written is very hard to follow, I had to rewrite my code twice because I did not know they had to MATCH exactly by length. I just thought that b had to contain the squares of a at least once.

indeed ! WTF.

Hahaha

The pop will return the last element, and if the element does not exists, they will return this element...

Perfect solution, and very different from mine!

what does -> do?
where is row declared in valid9?
can someone explain the code please?

couldn't you avoid the "series whose unique numbers add up to 45 but are not valid sudoku wins. For example 2, 2, 9, 9, 6, 1, 8, 14, 5 or 0, 0, 0, 0, 0, 0, 0, 45. " by doing row.uniq.size == 9

My code is working properly on my own tests, but not on the built-in test. Here's the error message.

Expected: 'HEY JUDE', instead got: 'HEY JUDE'

Any suggestions?

"...remember that you can access the preloaded Morse code table through MorseCode.get(code)"

This should say what it says WAY at the bottom of the dishonest description I got tired of reading:

"...codes can be decoded using the MorseCode.get() function. For example, MorseCode.get('.--')"

The description is WAY too long.

You put up a Wikipedia link to SOS where it clearly states "The first ship to transmit an SOS distress call appears to have been either the Cunard liner RMS Slavonia on June 10, 1909, according to "Notable Achievements of Wireless" in the September, 1910 Modern Electrics, or the steamer SS Arapahoe on August 11, 1909." and then you claim that the first use of SOS was the Titanic. Give me a break.

"import java.util.*;" ...What a great kata creator.

"Hello sorry for the late replay but usually setup doesn't include all the tools needed to complete the exercise."

BS! Your setup doesn't even include the tools to set it up!

Java tests are still the same problem they were a month ago.

Also, the test cases are all bunched together into 1 test instead of being separate tests.

This prompt sucked. Let me code not decipher Dr. Soose.

This may have worked in the tests but is incorrect. Try this code with "(123) 456-789999999999", for example.

It will only check the number until the first 9, and then pass it on to your calling software which will put in all the 9s. Imagine if a malevolent actor put in 911 at the end. (This could be another test throughout.)