No, you should reduce those fractions first.

This is necessarily coming from your code, there is no way tests magically multiply all numbers in your result by 10. When you don't know, please: don't raise an issue! See the documentation: https://docs.codewars.com/training/troubleshooting/

If I look at the second test data sample provided in the Elixir version:
lst = [ [690, 1300], [87, 1310], [30, 40] ]
testing(lst, [ [18078, 34060], [2262, 34060], [25545, 34060] ])

The GCD of 34060 is incorrect. 34060 / 1300 = 26.2, 34060 / 1310 = 26, and 34060 / 40 = 851.5. I did all the prime factorization by hand, checked my algorithm for LCM, as well as verifying with other sources, and the correct GCD should be 340600.

Enum.map_join/1 is a function.

Since it didn't specify UTF-8 chars, you're absolutely right. In that case, I would probably use String.graphemes() instead

I believe that byte_size works only when letters are from English alphabet. Any other letters are coded on two bytes

Try to avoid mutable variables in F# when possible. For this example, the explicit mutation is not necessary.

It's not necessary to declare min and max as variables. The final statement in an F# function will evaluate as the return value for that function

Thanks. I was pretty sure that I did check the spoiler flag, so I investigated further and found that when I click the text that says "Mark as having spoiler content" it doesn't actually mark it as having spoiler content. I have to actually click on the tiny checkbox. And that is true even though the pointer changes to a pointing-hand when hovering over the text, and the text is right next to the checkbox. Isn't it a UX standard at this point that clicking the text next to a checkbox will check the corresponding checkbox?

Your thoughts?

spoiler flag...

Will do! I should have one together fairly shortly.

Thank you for translation! Please add a test with very long array, so solution with sorting this array will fail on time limit, and O(n) solution will pass.

Float.to_string/2 is now deprecated and generates a compiler warning