Thicket currently has reader implementations that do not create a new Thicket from raw input data, but instead augment an existing Thicket with additional information. Two current examples are the NCU reader and the Static Compiler Info Reader introduced in #272.
These readers behave differently from traditional readers because their purpose is not to construct a Thicket from scratch. Instead, they modify or enrich an existing Thicket by appending new metadata, performance data, or analysis information.
As we add more of these in the future, it may be useful to classify these components as Modifiers rather than readers. This would allow us to create a clear disctinction:
- Readers, which construct a Thicket from an input source.
- Modifiers, which operate on an existing Thicket and augment it with additional information.
A first step could be to introduce a dedicated modifiers/ directory where these implementations can live, rather than adding each new augmentation method directly to Thicket.py.
Thicket currently has reader implementations that do not create a new Thicket from raw input data, but instead augment an existing Thicket with additional information. Two current examples are the NCU reader and the Static Compiler Info Reader introduced in #272.
These readers behave differently from traditional readers because their purpose is not to construct a Thicket from scratch. Instead, they modify or enrich an existing Thicket by appending new metadata, performance data, or analysis information.
As we add more of these in the future, it may be useful to classify these components as Modifiers rather than readers. This would allow us to create a clear disctinction:
A first step could be to introduce a dedicated
modifiers/directory where these implementations can live, rather than adding each new augmentation method directly toThicket.py.