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
When calculating things like integrity hashes (used by recent Bazel releases), it's helpful to be able to base64 encode and decode values. Starlark does not offer a mechanism to do this natively, though it may be possible to write one in pure starlark. Having a native implementation would be significantly faster (as we saw with JSON processing)
The text was updated successfully, but these errors were encountered:
It seems like this would be supported by a string <-> bytes encoding/decoding API. So I think this is blocked on finalizing bytes support in the spec (the list of methods, which are currently TODOs).
One relevant question is whether base64 would be listed in the spec as a required supported encoding for any implementation.
When calculating things like integrity hashes (used by recent Bazel releases), it's helpful to be able to base64 encode and decode values. Starlark does not offer a mechanism to do this natively, though it may be possible to write one in pure starlark. Having a native implementation would be significantly faster (as we saw with JSON processing)
The text was updated successfully, but these errors were encountered: