[Enhancement] Allow for multiple versions of the same day

[walkerboh]

Sometimes when I solve a day, I take one approach to complete it, but once I've finished it, I think of a novel approach that I would like to try but I don't want to lose my original solution, and if possible, I would like to compare the performance of the two. Would it be possible to support class names like Day01b or something similar that allows us to register multiple solutions for the same day and have them appear in the results?

[eduherminio]

Thanks for the feedback @walkerboh.
You're right there's no support per se for multiple day solutions, I'll take that into account for future improvements.

You can try to use the following workaround: overriding uint CalculateIndex().

i.e.

using AoCHelper;

await Solver.SolveAll();

public abstract class MultipleSolutionsDay : BaseDay
{
    public override uint CalculateIndex()
    {
        var typeName = GetType().Name;

        return uint.TryParse(typeName[(typeName.IndexOf(ClassPrefix) + ClassPrefix.Length)..].TrimStart('_').TrimEnd(['a', 'b', 'c', 'd']), out var index)
            ? index
            : default;
    }
}

public class Day_01a : MultipleSolutionsDay
{
    public override ValueTask<string> Solve_1()
    {
        Thread.Sleep(1_000);
        return new("Solution to part 1");
    }

    public override ValueTask<string> Solve_2()
    {
        Thread.Sleep(2_000);
        return new("Solution to part 2");
    }
}

public class Day_01b : MultipleSolutionsDay
{
    public override ValueTask<string> Solve_1() => new("Solution to part 1 - optimized");

    public override ValueTask<string> Solve_2() => new("Solution to part 2 - optimized");
}

public class Day_02 : MultipleSolutionsDay
{
    public override ValueTask<string> Solve_1() => new("Solution to problem 2");

    public override ValueTask<string> Solve_2() => new("Solution to problem 2");
}

I'm aware it's not ideal because:

• The suffix isn't shown then printing the results, so if they return the same solution (as they 'should') there's no built-in way to make it obvious how to distinguish them unless manually adding a suffix to the solution yourself.
  This is something I might solve in the future, allowing to customize the names
• SolveLast() will only solve one of the implementations of the same day, not the multiple implementations of the same day
• etc.

But maybe it can temporarily help you.

[walkerboh]

Yeah, I did look at overriding CalculateIndex but I wasn't sure if that would cause an issue for the solver. Appreciate the work around for now at least.