Potential floating point errors before rounding in Java.
Unlikely given the limited number of operations but possible.

Fork that fixes it

Description should be changed to either remove "which can be positive or negative," or explicitly state that 0 is an acceptable value. Otherwise, that clause sounds like a constraint on which integers are allowable.

C#: method name should be PascalCase (Please refer to implementation of backward compatibility here )

No random tests in

• C#

• Java

Missing fixed tests in C#

Modifying the input causes actual tests to break.

RISC-V Translation

I dont understand why using floor, round or ceiling does not gives different values
eg.
input 1 km/h => Math.Floor(1 * k) => output 29
input 1 km/h => Math.Round(1 * k) => output 30
input 1 km/h => Math.Ceiling(1 * k) => output 31

D translation

Hi. The original Java code template seems to be in C-style, while common Java convention is to have first curly bracket at the end of the first line of a method declaration.

https://www.cs.cornell.edu/courses/JavaAndDS/JavaStyle.html#Indentation

NASM translation