Uh oh!
There was an error while loading. Please reload this page.
Base64 library tests: use full encoding map - #71006
Merged
Merged
Conversation
InitializeDecodableBytes is skipping the last entry in the map, due to assuming it is an = sign. This was spotted whilst upstreaming: dotnet/performance#2479
ghost
commented
Jun 20, 2022
Tagging subscribers to this area: @dotnet/area-system-memory Issue DetailsInitializeDecodableBytes is skipping the last entry in the map, This was spotted whilst upstreaming:
|
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 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.
InitializeDecodableBytes is skipping the last entry in the map,
due to assuming it is an = sign.
This was spotted whilst upstreaming:
dotnet/performance#2479