fixed~

The example conversions have the units flipped. Should be ex. 24C = 20.1R

Enabled

Every translation now has approximate equality on the level of test checker, resolved

Done, I think I can close out this issue then ;^^

nahhh, if the kata was translated to C#, the signature would be CelsiusToRomer, doing this explicitly for each language with different naming conventions is not ideal as of current standards and is hard to maintain overtime.

So, the ideal approach would be to completely remove the function names, like just writing you've decided to write a function that takes...

As for the examples, the same generalized approach applies , something in the form of Input --> Output is sufficient. If solvers need to get a clearer idea, they may refer to sample tests which serve such purpose.

Added the different signatures for the first and reworked the example for each language for the second proposals, please check

Description should be language-agnostic in the meantime

Talking about these -->

celsius_to_romer()

For example: celsius_to_romer(24) should return 20.1.

Implicitly added the formula into the description, so now you don't necessarily need to go to Wikipedia for the formula.

fixed

1. Actual & Expected are flipped in the random test.

   test.assert_approx_equals

   test.assert_approx_equals(my_celsius_to_romer(1.0*temp), celsius_to_romer(1.0*temp))
   #                         ^^^^^^^^^^^^^^^^^^^            ^^^^^^^^^^^^^^^^
   

2. Please use random values for the random tests.

Technically, all translations are now using that formula (some of them are abs() < 1e-N, others have built-in test methods, but that's another story), therefore, this suggestion may be resolved

Python fork which resolves this problem at least for Python