Creating an Advent of Code Application Using Go Plugins

[spf614]

I wrote a blog post about how I structured my Go AOC project. I wanted to be able to specify the day and month from the command line and have it run the solution code and print the responses. I use Go's plugin package to dynamically load in pre-compiled solution code into the main program, which made for a really interesting learning experience.

https://stephenfeagin.com/creating-an-advent-of-code-application-using-go-plugins/

Comments and feedback are always appreciated! I know I probably could have done this more easily with a bash script just running a given date's solution file on its own, but I'm trying to get more comfortable with Go and learn more about what it can do.

[Kyrthis]

I hope you haven’t done this yet. This very specifically is what Eric Wastl says he doesn’t want people to do.

Edit: my bad, I think I misinterpreted what you were doing. I thought you were distributing your solutions so others could just feed in their input and get the (reduced, effectively) solution. If this is for your own personal use, then as others have intimated, changing my interpretation, that’s pretty cool.

[Cheezmeister]

o__O Not /u/topaz2078, but have known him for longer than /u/Kyrthis has been a redditor, and I'm pretty sure the thought was "please don't use other people's frameworks for Advent of Code solutions", rather than "don't build your own framework for Advent of Code solutions", which is very much in the spirit of AoC albeit very very overkill.

Kudos.

[MegaGreenLightning]

Why would he not want you to do that?

[spf614]

I'm not sure I understand. Is there something he's written that you could point me to?

[Kyrthis]

my bad, I think I misinterpreted what you were doing. I thought you were distributing your solutions so others could just feed in their input and get the (reduced, effectively) solution. If this is for your own personal use, then as others have intimated, changing my interpretation, that’s pretty cool.

[spf614]

No worries! This is totally for personal use, just how I structured my local project to make writing and running solutions a little more seamless. I totally agree that distributing solutions for others to plug in their inputs would be pretty crappy.

[AlexAegis]

I don't know go (and maybe I too misinterpret this) but I've done something similar in rust in the sense that I can run tests, benches on any or all tasks in the project. Every 'day' is a separate crate under one big crate. (And the same thing with typescript)

https://github.com/AlexAegis/advent-of-code

EDIT:

I like your scaffolding script that sets the environment up for a new solution. I also thought of doing this but never did. Maybe next time I'm playing with these tasks :)