M.V. Hutz
609fe05250
## Description This PR adds benchmarking capabilities to the lambda interpreter. The benchmarks measure performance across all sample files in the samples folder. This enables consistent performance testing and helps track optimization improvements over time. Changes in this PR: - Added new `bench` target to Makefile for running Go benchmarks. - Created `benchmark_test.go` with sub-benchmarks for each sample file (Church, Fast, Saccharine, Simple, Thunk). - Used `b.Run` for organizing sample-specific sub-benchmarks and `b.Loop` for efficient iteration. - Configured benchmarks to use fixed iterations (10x) and 4 CPU cores for reproducible results. ### Decisions Used `b.Loop()` instead of traditional `for i := 0; i < b.N; i++` pattern. This is the modern Go benchmarking idiom that provides better performance measurement. Benchmarks run the full pipeline (parse, compile, execute, stringify) to measure end-to-end performance for each sample. ## Benefits Provides quantitative performance metrics for the lambda interpreter. Enables tracking performance improvements or regressions across different sample complexities. Consistent benchmark configuration (fixed iterations, CPU cores) ensures reproducible results for comparison. ## Checklist - [x] Code follows conventional commit format. - [x] Branch follows naming convention (`<type>/<description>`). Always use underscores. - [x] Tests pass (if applicable). - [x] Documentation updated (if applicable). Reviewed-on: #14 Co-authored-by: M.V. Hutz <git@maximhutz.me> Co-committed-by: M.V. Hutz <git@maximhutz.me>
1.4 KiB
1.4 KiB