Skip to content

Benchmark: Move file/path setup and compiler wiring out of benchmark body #32

Description

@jozefizso

Current: Each [Benchmark] constructs paths, reads from disk (data/Class.vb, data/Module.vb), and creates/configures VbaCompiler inside the timed method. This measures setup/IO more than compile performance.
Proposed: Shift path resolution and VbaCompiler construction/module/class registration into [GlobalSetup] or [IterationSetup]; leave the benchmark body to only call the compile method(s). Consider a separate benchmark if measuring setup is desired.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions