That's a great move right here! well done !!

its called aliasing..

number_to_string = str

its like instructing python that str has another name as well, namely 'number_to_string'.

In a sense Probably True is arguably better than running virtually forever with no result. :P

Hey, that's my favorite primality test! Nothing else would come to my mind when testing larger numbers. In practice, 5 rounds is more than enough in most cases, don't need 40. :P

es mas effectivo porque hace operaciones en binario.

aumenta el tiempo de ejecución.

Rust: The tests seem to have issues.

I got this compilation error:

error[E0308]: mismatched types
   --> src/lib.rs:129:9
    |
129 |         assert_eq!(partitions(n), size);
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `usize`, found `u32`
    |
    = note: this error originates in the macro `assert_eq` (in Nightly builds, run with -Z macro-backtrace for more info)

For more information about this error, try `rustc --explain E0308`.
error: could not compile `challenge` due to previous error


NOTE: Line numbers in error messages can be incorrect due to concatenation.

I suspect the size variable in the test is u32 instead of usize.

nerd :P

Nice kata, but would have like to see tougher tests. Maybe go up to 1000?
Also, it would be good some form of anti-cheat, upper limit for characters perhaps?

done

approved

Thanks for the detailed explanation of this approach.

Dayum thats a smart move