Base64 does not support streaming data
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
I created this issue after opening the PR here (https://github.com/uutils/coreutils/pull/8622), but it tracks the problem.
The main issue is that that the current base64 implementation needs to read the whole input to be able to distinguish whether there is padding or not. However, padding is only in the end, so the solution for that can be avoided by just checking at the end of the file.
This works differently in GNU Coreutils, and there you can see also the low memory footprint.
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 by reviewing the current base64 implementation and the referenced PR 8622. Compare its input handling with GNU Coreutils, focusing on how padding is detected at end of input. Done means base64 supports streaming input without reading the whole input and achieves a similarly low memory footprint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100