Streamline SC_GetNextRtsCommand and SC_ParseRts
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C
- Stars
- 46
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
Both functions use temporary buffers and potentially unnecessary copies.
Imported from GSFCCFS-1471
Contributor guide
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
Locate the definitions and callers of SC_GetNextRtsCommand and SC_ParseRts, then trace how their temporary buffers are used. Compare the current data flow and copying behavior before deciding whether the functions can be streamlined. Done means the behavior remains unchanged while unnecessary temporary buffers or copies are removed and the relevant project tests still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100