aoc-toolbox-derive

Crates.ioaoc-toolbox-derive
lib.rsaoc-toolbox-derive
version
sourcesrc
created_at2022-07-21 14:05:03.441986
updated_at2024-12-03 17:14:19.760779
descriptionMacros implementation of aoc-toolbox
homepagehttps://gitlab.com/RomainGiraud/aoc-toolbox
repositoryhttps://gitlab.com/RomainGiraud/aoc-toolbox
max_upload_size
id629665
Cargo.toml error:TOML parse error at line 17, column 1 | 17 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include`
size0
RomainGiraud (RomainGiraud)

documentation

https://gitlab.com/RomainGiraud/aoc-toolbox

README

aoc-toolbox

📖 About

aoc-toolbox is a Rust library designed to simplify your Advent of Code experience. With this toolbox, you can:

  • Mark your solvers with minimal boilerplate.
  • Automatically generate a main function with argument parsing.

📦 Installation

Add the following dependency:

cargo add aoc-toolbox

🚀 Usage

1. Mark Your Solvers

Use the #[aoc_solver] macro to annotate your solver functions. For example:

use aoc_toolbox::aoc_solver;

#[aoc_solver("day01", "part1")]
fn solve_part1(input: String) -> String {
  // Your solution logic here
}

2. Generate the Main Function

Use the aoc_main! macro in your main.rs file to tie everything together:

use aoc_toolbox::aoc_main;

mod day01;

aoc_main! { 2024 }

3. Provide Input Files

You must provide a .txt file as input for each day, located at: input/day01.txt. The solver will automatically load the appropriate file based on the selected day.

How It Works

The aoc_main! macro will generate a main function that:

  • Parses the command-line arguments.
  • Runs the specified solver for the selected day and part.

Example Command

cargo run -- --help
cargo run -- --list
cargo run -- day01 # run all solvers for day 1
cargo run -- day01::part1 # run a specific solver

⚠️ Limitations

  • Macro State: Rust macros do not currently share state between calls (see this issue). A workaround is implemented, but it may lead to unexpected behavior.
  • Solver Signature: Each solver function must take a String as input and also return a String.

💡 Motivation

This tool was initially created for personal use during Advent of Code, but it's now available for anyone who finds it helpful. Enjoy hacking away at those puzzles! 🎄✨

Commit count: 36

cargo fmt