Missing fixed and samples tests for following cases: (TODO: check in all languages ~~

• m = 0, n = 0

• m = 0, n = 1

• m = 1, n = 0

Ok, I got it.
Setting the input type as u32 is to ensure the data remains within that range.
The output type is set to u64 to prevent overflow in the result.

However, the description doesn't specify the input range.
Therefore, using u64 for the input type is also a valid choice.

i guess because the output will always be bigger than the input. returning a u64 allows the function to potentially handle very large inputs

In Rust, why is the input type u32 instead of matching the output type u64?

noone can help you unless you determine your problems sir!

it's a bad desc!!!!!

The trick is that you can solve it without understanding the problem.
Just check at the suggested answer and produce an algorithm that will produce the expected answer.
It's a no-brainer.

Are you sure it's not 46x0 ?

it happens!

Fixed.

Actual and expected are swapped in PHP