-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Update windows imports to use 'W' functions #1773
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
Conversation
|
Are new tests desired for these pulls? I made some locally, but wasn't sure if they were wanted. |
daurnimator
left a comment
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.
I have 0 context here, but are you aware that windows doesn't use well-formed UTF16? This ill-formed utf16 is not safely convertible to utf8. When converting you have to use "WTF-8" instead.
|
@daurnimator thanks - I filed #1774 in response to your comment. |
andrewrk
left a comment
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.
Looks good - an optional improvement and a minor documentation addition and then it's ready for merge.
Tests would be much appreciated |
|
Code has been updated for review.
|
|
Im not sure why the pipeline is stopping where it does |
|
@andrewrk which env variables should i have the tests look for? |
FreeEnvironmentStringsAtoFreeEnvironmentStringsWGetEnvironmentVariableAtoGetEnvironmentVariableWGetEnvironmentStringsAtoGetEnvironmentStringsWos.getEnvMapto use the stack for environment keys and values with a length under 50 to be built on the stack; anything larger is allocated on the heap.Addresses #534