Sample Policy Provider SecOp ordering creates intermediate list before appending to Action
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14
- Forks
- 9
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 33
Description
Could be an optimization, some options:
-
Expose API in
SecurityAction.htoset_atto avoid this list. BUT: it would be by-copy instead of by-move, The M-Array doesn't provide API forpush_move_at- can onlypush_movewithout specifying location andset_atas pass-by-copy. -
Creating a function in
SecurityAction.hto "sort" the SecOp list using a PP-defined comparator, and using the m-lib's_special_sortAPI. This way, the actual ordering is still PP-specified
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
Start with src/policy_provider/SamplePolicyProvider.c around lines 220-297 and review SecurityAction.h, focusing on how the SecOp list is ordered and appended. The issue presents multiple API and sorting options but does not select an approach; done would require an agreed implementation that avoids the intermediate list while preserving provider-defined ordering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100