Skip to content

Move the notion of variants to FlowCfg #165

@rswarbrick

Description

@rswarbrick

These are defined and handled in child classes (including SimCfg), but that's a bit odd, because a variant is something about a mode of the design rather than a mode of the testbench.

Move them to FlowCfg, which will probably make more sense (and, I suspect, will also simplify some code)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions