Agree that this one was less fun, and I kind of hate my Python solution, which is much muddier than yours. I don't know that I have the energy to try to do this in Go.
Yeah, I like the algorithm-y ones, this one was more string parsing I think!
It was a complicated description though, I had a lot of problems parsing what I was supposed to be finding.
TOTALLY -- I only figured it out once I looked at the input. The graph actually totally threw me off.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Agree that this one was less fun, and I kind of hate my Python solution, which is much muddier than yours. I don't know that I have the energy to try to do this in Go.
Yeah, I like the algorithm-y ones, this one was more string parsing I think!
It was a complicated description though, I had a lot of problems parsing what I was supposed to be finding.
TOTALLY -- I only figured it out once I looked at the input. The graph actually totally threw me off.