You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
base64.Encoding.Strict was added in #15656, but there was no equivalent method added to base32.Encoding.
To be consistent, I propose we add the equivalent functionality but rename it. The name Strict is unhelpful since there are multiple dimensions that the encoding could be stricter on.
I propose adding the following methods to both base32 and base64:
// RejectNonZeroPadding creates a new encoding identical to enc except// that decoding requires trailing padding bits to be zero,// as described in RFC 4648 section 3.5.func (encEncoding) RejectNonZeroPadding(enablebool) *Encoding
and we deprecate the existing base64.Encoding.Strict method.
The text was updated successfully, but these errors were encountered:
This feature combined with #53845 makes it possible to implement a truly bijective mapping between baseXX and binary data. This would allow the use of base32 and base64 to produce a truly canonical encoding per RFC 4648, section 3.5.
base64.Encoding.Strict
was added in #15656, but there was no equivalent method added tobase32.Encoding
.To be consistent, I propose we add the equivalent functionality but rename it. The name
Strict
is unhelpful since there are multiple dimensions that the encoding could be stricter on.I propose adding the following methods to both
base32
andbase64
:and we deprecate the existing
base64.Encoding.Strict
method.The text was updated successfully, but these errors were encountered: