The given types are both i16. If you want to support bigger numbers the signature of the function has to be changed accordingly. Changing the types in the function on the fly is confusing at best. Giving back an error result in the case of an overflow would be the best practice.

noice!

feels like cheating

noice

Beautiful

A testcase could be n = 4000, m = 4000, which will evaluate to -96 in i16

An excellent point. Though for the scope of the problem it would hardly matter.

You don't need the extra parentheses if you wanted a cleaner oneliner

if there's an x in the string, then the input is invalid

Given a string made up of letters a, b, and/or c

good, but if input string have a "x" char this solution doesnt worked.

best.
very clever and clean => best practice 👍

100% it is a best variant, geez, genius and minimalistic

I didn't even think of that. I used if

Approved some time ago

• Updated Rust version to latest
• Slightly improved failure messages