Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-13407

Investigate the trade-offs of splitting _internal.h files by subsystems

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Storage Engines
    • StorEng - Defined Pipeline

      Description

      This ticket is the result of a comment in modularisation doc.

      As part of our ongoing modularisation efforts, we need to investigate the trade-offs of splitting our current single _internal.h file into multiple _internal.h files for each module/subsytem. Currently, we maintain a single large internal.h file, which offers convenience but compromises modularity

      Scope

      • Explore the feasibility and impact of transitioning to one _internal.h file per module/subsystem.
      • Assess the benefits and drawbacks
      • If feasible, propose a strategy for transitioning.

      Note: This is to be completed by the end of Q3, once we have modularised a subsystem.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            siddhartha.mahajan@mongodb.com Sid Mahajan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: