[DISCUSS] Prototype a Base64Encoder#2452
Draft
kinkie wants to merge 2 commits into
Draft
Conversation
yadij
added
the
M-ignored-by-merge-bots
Contributor
|
The only issue I see is that Squid base64 encoding is only used on buffers. So we would end up adding a stream just for the purpose of using the encoder. |
rousskov
requested changes
Jun 28, 2026
rousskov
left a comment
rousskov
left a comment
Contributor
There was a problem hiding this comment.
I had already flagged this API direction as problematic before this PR was posted. Will find time to detail that claim.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stemming from the converstaions in PR #2447 which focuses on
addressing a problem as narrowly as possible , here
is what I would envision a base64 encoder to look like.
It's a prototype, vibe-coded with lots of hand-holding on my side,
so please don't focus too much on the code itself, it comes with
a comprehensive unit test which is meant to showcase the API.
Does anyone see anything obviously wrong with the approach or is
it worth investing into by reviewing, polishing, writing a decoder and using it?