• Breaking retrocompatibility
  • Keeping retrocompatibily requires:
    • Filtering hits and creating new HitPatterns filled with hits of one category only (TRACKER/EXPECTED_INNER/EXPECTED_OUTER)
      • Lazily created cache --> uses four times more memory at runtime (original + 3 filtered copies), some new/delete time overhead.
      • We can still have the hit category aproach mentioned before by adding a default category:
        • T trackBase.hitpattern().method() { return trackBase.hitpattern().method(this->defaultCategory) };
-- JuanAldea - 24 Feb 2014
Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2020-08-30 - TWikiAdminUser
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox/SandboxArchive All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback