Does anybody have some good tips to read-up on to prepare for AoC using Kotlin? A nice Kotlin Collections / group theory / software algorithms with Kotlin resource maybe?

frankly, there is no consistent algorithms+data structures library for Kotlin

I just started writing my own when I first started and kept reusing and expanding it each year as needed. There is mostly some stuff to deal with 2D points (x, y) coordinates and matrices (arrays of arrays)

Yeah, looking forward to learn more about the Collections API!

I wonder if there will be CRT again. It's like 3 years since we saw it last time

Well I have a generic A* lying around for such use cases

Do you have that laying around somewhere? Or just written it yourself based on the algorithm?

I just based it on https://en.wikipedia.org/wiki/A*_search_algorithm#Pseudocode

I see Ray Wenderlich has a book on Data Structures & Algorithms in Kotlin

Oh yeah, graphs are not my strong point either 😄

+ there’s always a catch… it’s never pure A*, or CRT, or what have you.

Nope, I remember one from last year where you had a grid with heights (like a relief map) and you could go up or down 1 step (but not more) and had to find the shortest path from a given point (maybe the lowest point) to the 'peak'

also just for some general input parsing etc there is this old but good blog post

Thanks Maia! Will definitely read!

We’ve also recently released an Algorithmic Challenges in Kotlin plugin-based course, prepared by competitive programmers and experts in algorithms. Maybe this could help. And we’ve gathered previous years’ solutions here.

I don't think there has been a single day where you needed A*, BFS or Dijkstra is usually enough.

Hehe yes... Now you reminded me of

uses crt;

from turbo pascal 😁

I have a method called 'crt' in my util library that aids in the printing of list of lists of booleans as grid. I might need to rename that then

It was the puzzle about some encoding, right?

Doing this in the project template’s

Utils.kt

file…

fun String.readLines(): List<String> {
    croakIfUsingSampleInput()

    return File("src", this).readLines()
}

private fun String.croakIfUsingSampleInput() {
    if (contains("sample")) {
        "❌❌❌ 🧝 YOU ARE USING SAMPLE INPUT ⚠️".println()
    }
}

… since I lost some time on not finding the right answer because I used sample input, instead of the real input last year 😅

I always have my code as a

fun

in the

main

source set, independent of any inputs, with a

main()

function that runs it on real input (which is stored as a resource), and at least one

@Test

function in the

test

source set for each sample input

Nice approach @ephemient!

out of curiosity - how does --continuous work if you edit source while previous run is still going?

yes, it'll start another run right after the previous one

but in case the when previous version goes into some infinity loop or something, you need to kill it manually?

yep. don't write infinite loops 😛

(or add

@Timeout(600)

or something 🙂

Spent some time generalizing my setup, so basically: I can start implementing a new day by just adding a package "dayX" with contents "DayX.kt" (actual implementation with a class which extends Day which has default methods to get the answers for part 1 and 2), "DayXTest" to have tests (yes this is also in src/main/kotlin instead of src/test/kotlin just to make it easier for this project), "X-example-N.txt" with some example input and "X.txt" with the actual input

> + there’s always a catch… it’s never pure A*, or CRT, or what have you. At least with the pathfinding algorithms, the standard versions usually work. The CS class adjacency matrix versions don't usually work because oftentimes you can't efficiently calculate all the edges in advance. But if you have a version that lets you generate edges on the fly through a function or lambda, you're good to go.

Hi @ephemient - I’m playing with your idea of continuous gradle testing, seems useful, but did you manage to suppress the

* What went wrong:

and

* Try:

sections from gradle output? Say in case of error, I’d only want to see

Day0Test > part1test() FAILED
    org.opentest4j.AssertionFailedError: expected: <333> but was: <334>

3 tests completed, 1 failed, 1 skipped

FAILURE: Build failed with an exception.

to minimize the screen clogging. Do you maybe handle it somehow?

perhaps you can use

./gradlew -q

with customized test logging settings

ah ok, that’s one way to solve it. the report file placement does not change so it can be open in brower…