libmfu: support MPI_FLIST_NULL to be passed to functions
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 200
- Forks
- 85
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 2
Description
Treat such as argument as an empty list on which nothing can be changed, or perhaps looks for this and bail with an error. Examine whether this makes sense across the full set of mfu_flist calls. If this is reasonable, it's nice to do this to simplify code calling libmfu since the user code can then avoid a bunch of if/else logic this way.
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
Begin by inventorying the full set of mfu_flist calls in libmfu and tracing how MPI_FLIST_NULL is currently handled. Resolve whether it should behave as an immutable empty list or cause an error, then verify that the chosen behavior is consistent across the affected calls and that callers can rely on it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100