Uh oh!
There was an error while loading. Please reload this page.
Update windows imports to use 'W' functions - #1773
Conversation
suirad
commented
Nov 22, 2018
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.
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.
andrewrk
commented
Nov 23, 2018
@daurnimator thanks - I filed #1774 in response to your comment. |
andrewrk
left a comment
There was a problem hiding this comment.
Looks good - an optional improvement and a minor documentation addition and then it's ready for merge.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
andrewrk
commented
Nov 23, 2018
Tests would be much appreciated |
Code has been updated for review.
|
suirad
commented
Nov 25, 2018
Im not sure why the pipeline is stopping where it does |
suirad
commented
Nov 30, 2018
@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