How tmcg/adventofcode2023 works
Main Components
a) Project Structure Layer
• Root Project Container
• Daily Challenge Modules (day-01 through day-10)
• Shared Library Module
• Template Generation System
b) Build and Development Layer
• Cargo Build System
• Just Command Runner
• Cargo Generate Template System
┌─ Project Architecture ─────────────────────────────────────┐
• ┌─ Development Tools ─┐ ┌─ Template System ─┐ │
• Just Commands │ │ - Template Dir │ │
• Cargo Build │ │ - Cargo Generate │ │
• ┘ │
• ↓ │
• ┌─ Challenge Modules ──────────────────────────┐ │
• ┌─ Day-XX Module ─┐ ┌─ Shared Library ─┐ │ │
• Source Code │ │ - Common Code │ │ │
• Input Files │←─│ - Utilities │ │ │
• Problem Desc │ └────────────────┘ │ │
• ┘ ↑ │ │
• ↑ │ │ │
• ┌─ Day-XX Module ─┐ │ │ │
• Source Code │─────────┘ │ │
• Input Files │ │ │
• Problem Desc │ │ │
• ┘ │ │
• ┘ │
• ┘
Key Elements to Highlight
a) Module Independence:
• Each day module is independent
• All days share common structure
• Shared library provides common functionality
b) Development Workflow:
• Template-based generation of new days
• Standardized testing and running procedures
• Consistent project structure
Important Relationships
• Template System → Day Modules (generation)
• Shared Library → Day Modules (dependency)
• Just Commands → All Modules (execution)
• Cargo Build → All Modules (compilation)
Additional Notes
• The modular nature of the challenge solutions
• The automation tools for development
• The standardized structure across all days
• The role of shared components
• Component types
• Command relationships
• How to add new challenge solutions
• Where to find common functionality
• How the build and test system works
• The overall project organization
The level of detail should be sufficient to understand the project structure while avoiding implementation-specific details of individual challenge solutions.