-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Fix #31502 #31557
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
Fix #31502 #31557
Conversation
Can you edit the commit message to explain what's going on as well? It helps to have some more context than just "Fix #XXXX" Otherwise looks good to me, though, thanks! |
b84b342
to
dc97023
Compare
Signed-off-by: Peter Atashian <[email protected]>
Renamed commit message. |
Can you extend the unit test to make sure the new version indeed fixes the bug? How about calling |
The unit test won't actually test that branch since it requires |
This is the simple solution. I know @nodakai was working on a more complex solution that overhauled the `fill_utf16_buf` stuff. r? @alexcrichton
Oh, I didn't notice we had a run-pass test specifically for that. I guess it could benefit from a more aggressive check. That said, since this PR already landed I'm rather unmotivated to adjust that test. |
This is the simple solution. I know @nodakai was working on a more complex solution that overhauled the
fill_utf16_buf
stuff.r? @alexcrichton