-
Type: Task
-
Resolution: Unresolved
-
Priority: 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.