Grégory Obanos

`cargo aoc` relies on metadata provided by `aoc-runner` & `aoc-runner-derive`. You can find how to set them up in [aoc-runner documentation](https://docs.rs/crate/aoc-runner/latest). I do agree the error message should be improved.

Procedural macros don't give access to full reflection, so I don't think I can support both traits. I think can create a special case for `Vec` though. Right now, the...

It might be possible to read `Cargo.toml` features section and add them to the template crate run by `cargo aoc`.

The main issue is how symbols are exported by `aoc_lib`, in order to be used by `aoc_runner` and `aoc_generator` (which are year agnostic ATM).

If I recall correctly you can add `part1` or `part2` to the generator meta in order to use it only for a single part.

I mean mark your "global" generator with `partX` and the other part should immediately get the default generator.

Hum, input is trimmed to ease parsing (for example, when parsing a number on each line) here : https://github.com/gobanos/cargo-aoc/blob/52164cec883489167ad0bd4c6a6229aa588ea123/aoc-runner/src/lib.rs#L17 There is currently no way to turn it off :/

You're right, a flag to prevent trimming could be nice. After a glance at some old inputs, it still seems like a good default to me.

Oh, it might have something to do with re-exported `Result` types, I'm planning a new release before December 1st, and I'll make sure to use full path results each time...

Should be quite easy to implement, and we already open a browser tab for criterion results, so it should be possible to open the puzzle page after submission.