Refactor ClassFileImpl to allow loading Option classes lazily

XMLWordPrintable

    • Type: Sub-task
    • Resolution: Fixed
    • Priority: P4
    • 24
    • Affects Version/s: None
    • Component/s: core-libs

      The way the ClassFileImpl is written today we'll eagerly load all possible Option classes up front. By refactoring - have ClassFileImpl store Option instances and default to null values - we can make this lazily loaded (only load, say, DeadCodeOption if a user provides it)

            Assignee:
            Claes Redestad
            Reporter:
            Claes Redestad
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: