Thank you :-)

Hey, sorry for the late response. Thanks!

While it looks good to me, I unfortunately can't approve my own translation.

• Updated to Rust 1.54
• Updated function signature for rand's gen_range()
• Updated description

• Fixed a merge conflict due to the change in description

Great spot!

I have added that case and to the description as well, as it aligns with what is described:

• There may or may not be whitespace between numbers and operators.
• An addition to this rule is that the minus sign (-) used for negating numbers and parentheses will never be separated by whitespace.

It would seem to me that the added case, 1--1, would then be valid.

If you are okay with the kata in this state, I'll ask one of the other contributors for approval.

• This should solve the merge conflict due to the Prolog translation changing the description.

Ha, yes, I only heard afterwards that it could not be changed, unfortunately.

I have forked it.

Thanks for taking a look!

Thank you :-)

Oh, cool. And due to it being Cow I assume it saves some calls to .to_owned() for the else branch, as Join takes &str.

I'll look into this some more. Thanks for the fork! :-)

Oh, interesting! Do you mind explaining what exactly the difference is in this case? I thought it would end up calling .to_owned() on the string slice regardless?

https://doc.rust-lang.org/src/alloc/string.rs.html#2234-2240

Thanks for taking a look!

Forked, updated to 1.50 and hopefully fixed.

It should be fixed here: https://www.codewars.com/kumite/60637c75fb053700324c175d?sel=60648e7477c71400430cb9df

It should be updated now.

Mods can now approve translations without waiting, so that should help with fixing merge conflicts.

This is nice! I didn't know that.

Got it! :-)