4 years later still there rip

I was thrown off when using words as a name and accidentally shadowing the global. Not a huge deal, but I would prefer the global to be all caps, or passed in explicitly.

I see there are some sadists on the CW?)

Actually, I prefer for people to think they have a good solution after passing the sample tests only be to shocked that their solution is not complete at all. IMO it gives a good lesson to take more care to read the kata requirements carefully and not be too hasty in thinking you are finished without considering edge cases.

reduce with lambda: ehh.
reduce without lambda: beautiful.

Sample tests (in Python) are too easy, delaying all the good stuff for the real tests. We could use one that sets the same attribute twice, for example.

Good kata for trying again in different ways, with different approaches

I think most people will assume that the operations "consume" their inputs, and they would be right. But yeah, the description should state it anyway, just to be clear.

Some solutions mutate position and while that doesn't break the meaning or the tests, it does feel "wrong."

it should definitely be in the specs. examples are not specs.

the description should be correct, complete and consistent without the examples.

Okay, it is pretty clear in the examples. I admit I skimmed over them. But a tiny line could be added to the description when it's talking about precedence for other things.

It's unclear what the goal is -- performance? type checking? -- my solution passed before I even started to address either

Python updated; around half the solutions did get invalidated.