Rules for rounding are underspecified w.r.t. handling ties and most probably they are inconsistent between languages.

Crystal tests were tricky to update because default rounding mode changed from half-up to half-even between Crystal 0.24 and 1.0, and hardcoded values for fixed tests were not correct anymore.

Instructions don't specify how break time should be distributed between breaks

python/js reference solutions don't produce same answer for day_plan_solution(1, 3, 1) due to differences in language-built-in round

python: missing fixed tests that test the rounding behaviour

example of incorrect (sometimes) passing solution: https://www.codewars.com/kata/reviews/581e4b3fed2e5b6e3d000021/groups/6573479cce1f7d00010b1f59

Ruby 3.0 should be enabled.

Kata passes in 0 tasks occasionally in random tests, behavior for which is undefined. (JavaScript)

(Also, yes, I know that the tests cannot be changed. It's important to have an open issue in case that circumstance changes in the future, and to make others more aware of the issue that encounter it.)

@alexis-l8,

• Python 2 is unavailable
• Typos in the description:
  • alloted -> allotted x 2
  • througout -> throughout

Thanks!

1st question: The second example given in the instructions doesn't seem right to me. If you have 3 hours available, that's 180 minutes. If there are 5 tasks, each taking 30 minutes, that's 150 minutes. So 180 - 150 = 30. 30 divided by 4 would round to 8, so wouldn't the solution be [30, 8, 30, 8, 30, 8, 30, 8, 30], instead of the message about not sleeping? (I need my sleep!) Or am I misunderstanding something?

2nd point: It seems absurd to list break times that last 0 minutes. That's not a break. I think that should be reflected in the return value -- maybe something like, "You can sleep tonight, provided that you work straight through your day without any breaks, like a public school teacher." ;-)