You mean did we take full advantage of the language syntax and semantics? Yup! I did something similar to you, see my post for more details: Advent Of Code 2018 - #19

I was comparing with a JavaScript developer’s solution, and ya… Elixir is really nice I don’t feel like I cheated, but I definitely felt like I had it easier.

Using the documented functions of the standard library is not cheating. In a first go I just try to solve them. Speeding things up, making code idiomatic, all these cosmetic stuff is done afterwards, if at all. Massively depends on the time slot I can alot

I have not used String.myers_difference/2 though, because I was unsure if there are any guarantees about the order of :del and :ins keys. Also just filtering on the hamming distance beeing exactly 1 and then removing the opposing character by a |> zip(b) |> filter(fn {a, b} -> a == b end) |> map(fn {c, c} -> c end) |> to_string felt much more clean to me than matching on the diff-description in your version.

To make this overall easier, I dealt with char lists in this exercise.

I wouldn’t say that there is such thing as cheating in AoC. For me, these puzzles are about the goals you set for yourself. Many people just like to solve them for fun, and reach for whichever improvisation can help them. For example, one friend solved a puzzle last year on a piece of paper, and a few others by using grep from command line

When I did AoC last year, my main goal was to practice streams. I also tried to reach the solutions I’m happy with. In some cases, even after solving the challenge, I’d spend a few more sessions (sometimes even spread over a few days) to improve the solution.

So in my view, you set your own rules, and decide when you’re happy with your solution.

Wait…are you wondering if you’ve cheated because myers difference is a thing that exists in elixir or because you’re making an assumption that the wrong letter is only ever in the middle and not at the beginning or end? In the later case I’m not sure if this solution would work as a general solution for all inputs or not. It doesn’t really matter since you’re only using your input to work with I suppose.

Oh, this is a very valid point. I never have seen this issue before (as in: that this might become a problem).

Besides my points about ordering guarantees of inserts and deletes in the list, this is another point to consider against the general use of myers_diff here.

But still I do not consider this any cheating, as it solves the puzzle with the given input, which is the most important thing.

Last year, I followed the reddit actively, and some of the top-players said, they never touch again a solutions that gave them the correct answer until they really have to or get bored in the 11 months inbetween.

So it seems that there seems to be some kind of consensus, that whatever works, counts, well unless you simply copy paste

Yeah, a friend mentioned on twitter that there was a hack for this problem where you can make assumptions about the inputs and eliminate a bunch of looping and checking. I’m not making a judgement either way. Whatever solves the problem seems fine to me. Personally I wrote the O(n^2) solution similar to this since it was easy to understand and fast to write first. Once I had that I used the slow solution to validate a O(n) solution which seemed like a fun challenge.

I used String.myers_difference/2 along with Keyword.get_values, so it didn’t matter about the ordering, all the :del keys’ values will be checked, I think this is a lot better than pattern matching since it works when the differing character is in the first position. Also joining the :eq parts after with a similar approach was really easy. Kinda interesting how I’ve used Keyword.get so much but had never even heard of Keyword.get_values.

This was my solution if anyone’s interested.