-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Switch RhConfig from TCHAR to char #86393
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
|
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas Issue DetailsI don't think there's any reason for NativeAOT's
|
beeb6de to
6e6aed0
Compare
LakshanF
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.
Thanks for doing this! I assume we will test this more once EventPipe configuration option is enabled
| { | ||
| *value = true; | ||
| return true; | ||
| } |
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.
You can also delete TCHAR definition from src\coreclr\gc\env\gcenv.structs.h. I think it was there to make this work.
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.
Seems like some other parts of nativeaot are actually using the definition from there now. I might try to detangle in the future change, but I'm going to leave it for now.
I didn't see a reason for NativeAOT's
RhConfigto be useTCHAR-wchar_ton windows,charotherwise. We can hide away the details of reading the environment variable aswcharvscharand the embedded variables are embedded as ASCII (and read as such) already. This makes it stop usingTCHARfor the exposed API which seemed to just be more confusing to consume (this also makes it so thatRhConfig.hno longer just assumes some header included before it definesTCHAR/_T).