>> 1.0 / 0.0
inf
>> 0.0 / 0.0
NaN

according to evcxr, which is a rust REPL

The translation it's forked from didn't pass its tests

Haskell Translation

An annoying but possible solution might be to make a custom int subclass that checks for oversized ints, pass in a RestrictedInt(10) along with n, and disallow integer literals

You'd also have to ban the use of int, __class__, type, and Decimal.

But that would make it harder than other languages...

Edit: oops; it would still be possible to break the integer restriction using any default method that returns an int

Too much work to replace all the builtins and ban all the importables that would return int...

Java has no BigInteger prevention test at the moment;

I made a fork to add one in: https://www.codewars.com/kumite/6519ffe580f7c47d2e82a74c?sel=6519ffe580f7c47d2e82a74c

Rust Translation

Is this resolved?
I replaced the thrown exceptions with test.fail and the message except for the table one, but that one's caught an message'd in the table test.

Rust Translation
https://www.codewars.com/kumite/65054d57bc47bc00316babd1

Is this a reasonable translation? I used stack depth in bytes instead of counting frames.
I copied the anti-table measures as well, but I don't understand what they're combatting.

Rust translation

I don't understand why, but will do

I can't read your reply...

edit: I tried the forfeit this kata button and I still can't see your reply

I made a fork that adds in dyns and moves MEOW, MOE, and t_iso into preloaded to share between sample and real tests.