Better representation of segments in multi-segment records
Open
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 853
- Forks
- 322
- PR merge metrics
- No merged PRs in 30d
Description
The current implementation is rather fragile and hard to generalize at times. In particular:
- The
segmentsattribute is a list ofRecordorNoneobjects. Perhaps empty records could be represented with an empty-represented Record object instead. One cannot tell the segment length from the None object. - For variable-layout records, the layout record is read into the first segment. Maybe there should be a way to abstract away the layout record so that applications do not need to know about fixed vs variable layout records.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Record implementation and its segments handling, then compare fixed- and variable-layout records. Define how empty segments and layout metadata should be represented before changing code; done means callers can determine segment lengths without None values and need not distinguish fixed from variable layouts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100