stream_copy_to_stream's $offset argument is unclear
Nobody has claimed this yet.
- Dominant language
- XML
- Stars
- 596
- Forks
- 890
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 55
Description
Description
imo it should have been null-by-default since the beginning, only seeking if the user want it to seek for some reason, but i suspect that would be too much of a BC-break to fix today, however, $offset should be nullable, i should be able to do
stream_copy_to_stream(... offset:null);
instead of
stream_copy_to_stream(... offset: ftell($in));
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 with the PHP documentation entry for stream_copy_to_stream and read the current description of its $offset parameter. Check whether the documentation can clarify null handling and the existing ftell($in) workaround; completion would require an unambiguous parameter description and examples, or confirmation that the requested behavior belongs in PHP rather than its documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100