@ -64,12 +64,15 @@ Any questions please just get in touch!
## Solution
I had to assume that all the input data is well-formed and valid, and that instead of the actual time we're talking about a simplified version of the time (just a minute counter going from 0 to 59 and an hour counter going from 0 to 23, without any DST changes etc.)
Additionally it seems that there is a mistake in the test description: while the text seems to suggest that times are in HH:MM format (at least it claims this for the "current time" argument), the output example seems to use H:MM format. I've assumed that it is a mistake in example, and HH:MM format should be used (so the first line of the sample output is "01:30 tomorrow - /bin/run_me_daily").
I understand that you asked me to not use any existing libraries; I did not use any existing libraries for the solution itself, but there is a dependency on the test library to simplify writing tests. It does not affect the solution itself, only its tests.
Since you said that I can use any language I like, I decided to use Rust, because it's the only language I'm familiar with that offers convenient match syntax; and matches are very useful in this test.
I’ve decided to keep all code in a single main.rs file for simplicity.
This code can be run e.g. by `cargo run 16:10 <input.txt" (or `cat input.txt |cargo run 16:10`)
I've decided to keep all code in a single main.rs file for simplicity.
This code can be run e.g. by `cargo run 16:10 <input.txt` (or `cat input.txt |cargo run 16:10`)
