Thanks! I totally understand your reasoning and that's generally true that function's signature should be enough, but I am the case where full definition is useful as I'm writing that in IDE. I wrote that definition on my own which was working till some point, and this map(|n| Box::new(n)) was missing.

Thanks again, I really appreciate that!

Thanks for providing Rust translation.

Is that description complete?

impl TreeNode {
    /// Use this so you need not concern yourself with Boxing
    pub fn new(value: i32, left: Option<TreeNode>, right: Option<TreeNode>) -> Self
}

Any chances to have it provided in full shape?

Hi, that' wholesome set of Katas, thanks!

I am getting some issue in Rust, with random tests.
Let's see "jdtqzbq". After wololoing, that should be jdtpsbq, right? Because d between j and t is not changed, and then q just after t is changed to p. So we have 0 -2 0 3 1 2 -3, which reduces to 1 which says that Left won. But expected is Right side wins.
Am I doing something wrong on any step or something's wrong with calculating expected values?

Hi, message ValueError: sample larger than population simply says that population (from what we want build sample) is smaller than number of elements we want to select.
In this case it suggests that [x for x in c.dict.keys() if not str(x).startswith('__')] is less than 1. And that means that you miss something in class created with your solution.

Yep, it seems you're right @Blind4Basics, didn't notice Python version.

And yes, it's about missing delimiter at all @YuriyCherniy.

Interesting. Message TypeError: Can't convert 'NoneType' object to str implicitly does not look like from this code. Additionally I didn't received such error using your solution.
Please specify with which parameters you catch this traceback?

I'm new in go world, but wouldn't it create new string with each loop iteration?

It works like built-in split(). Hint: message you're writing about is Expected an error when empty delimiter!, that means that there is delimeter, but just empty..

Take a look on traceback. There you have printed line where issue happens.

Take a note that not all parameters need to be obligatory.

Thanks! I have to find a way to block it up someday.
But is it really an issue?

You're amazing guys. I will have to find a way to block these too!

You know what? I agree with you. I've learned a lot in past two years and I have to say that now I would ban this code during code review.

Glad to hear that! Thanks.
Maybe in future.

Thanks for this Kata, but I have to admit that I was somewhat confused by AND/OR in Description. So you wanted to have AND or OR condition?