-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: make EncodeAscii ghost #1286
base: main
Are you sure you want to change the base?
Conversation
Avoid slice
and a few other things
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but know that I'm concerned changing EncodeAscii will effect ESDK/DB-ESDK.
However, I'm a little confused, as I actually did not see a change to EncodeAscii, just changes at its various call sites?
The behavior of EncodeAscii did not change. The point of call changes went from
to
That is, explicit bytes, with an assert that nothing changed. |
Detected changes to the release files or to the check-files action |
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS |
Issue #, if available:
Description of changes:
Squash/merge commit message, if applicable:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.