Refactor exhaustiveness computation from Flow into a separate class

XMLWordPrintable

    • Type: Task
    • Resolution: Fixed
    • Priority: P4
    • 26
    • Affects Version/s: 26
    • Component/s: tools
    • None
    • b21

      The exhaustiveness computation is currently done inside the Flow class. But, it feels it is getting confusing as part of that class. The proposal herein is to move the exhaustiveness computation into a separate top-level class.

            Assignee:
            Jan Lahoda
            Reporter:
            Jan Lahoda
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: