A modern programming language that makes developers happier.

kotlinlang

Got my blog post done:
<https://todd.ginsberg.com/post/advent-of-code/2019/day3/>

Interesting choice about the `lazy`s, I'd just have them return a new instance every time. I have a feeling that could even beat the `Lazy` instance overhead.

<@U5UU34LPK> Yeah, that's totally fair. I could have just made them functions.

For part 1, if they cross at the origin, that would be the closest point thought right? Why would that be wrong?

&gt; While the wires do technically cross right at the central port where they both start, this point does not count
If they RE-cross at the central port, I would assume that's fine. But I don't think any inputs do. I'm happy to examine other inputs that AoC puts out though.

Karel - I thought about your advice and re-read my own writing on lazy and agree with you. No real good reason to have those as lazy properties. I went back and made them functions. Thanks for the code read! :slightly_smiling_face:

Thanks for your post series <@U35HN2RGQ>, it inspired me to get started on this AoC! I didn’t understand yet the difference between giving a solution to the puzzles and the private leaderboard…