Iterator::scan too limited
Open
Nobody has claimed this yet.
T-libs
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Surely for the simplest case, it works. However, the unfinished state may contain extra data that may hint us generate one or more Bs.
I believe the more sound way is call f for each item wrapped with Some(), and then call f with None until it yields None...
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
The issue names Iterator::scan but no files, tests, or entry points. Read the existing scan design and the discussion first; done would require an agreed specification for calling f with Some and None and for the resulting outputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100