Send your feedback or ask for help here!
I was surprised to see that in at least one validation test, there were multiple people with the same name, and they had to be treated as separate people (i.e., there was no identifier unique to a person). It turned out the names are completely superfluous and irrelevant to the problem. It might be a good idea to at least note in the problem statement that names are not unique.
Otherwise a very nice problem for easy level.
Hi to all and thanks @dolmen1234 (and validators @jddingemanse,@etig and @TBali) for this very interesting Puzzle.
→ It’s a good exercise (or review) about Dictionary usage => Good job !
Bye and good luck to all : have sun, fun and CodinGames …
It took me a long time to understand this, it should be clearly explained…
@dolmen1234, can you do it please ?
Nice puzzle otherwise.
Given that two persons (@sammck, @Statisticiah) react to the issue of non-unique names, my reaction as approver:
I ran into the same issue while approving this contribution. However, in my opinion it just adds an extra challenge to the puzzle - it forces you to do some debugging and error finding. While it is not explained in the statement that it is possible to have duplicate names, it is also not stated that this is not the case. I think it is fairly common for contributions to have edge case surprises waiting for you in later cases.
It took me some time to find and solve the error - but it was (in my case) a good reminder that python cannot have duplicate dictionary keys .
Doesn’t the visible “Formulas repeating” test also feature non-unique names?
Also, for most of the time, there shouldn’t be situations covered in validators but not covered in tests, and situations = general aspects and not minute details. I would regard non-unique names as falling into the category of general aspects.
@5DN1L ; I’m not sure I fully understand. Your point is that there is a problem here or not? The non-unique names is both appearing in the test and the validator indeed - if it would only appear in the validator, it would be a problem, but that is not the case here. I do agree non-unique names is a general aspect rather than a minute detail (or, rephrased: it is something your code should certainly take into consideration).
My point is there doesn’t seem to be a problem with this puzzle, yet when sammck and you write about it, you both seem to imply that the non-unique name situation appears in a validator only, but not in a visible test, and that makes me confused.
And oh… maybe you write “validator” when you mean “approver”…
Ah I understand the confusion. Edited my post to write ‘approver’ instead (though, at the start of this thread, it states ‘validated by…’, making me a validator ).