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
Implement NativeCall wide string support #1137
base: main
Are you sure you want to change the base?
Conversation
It's ridiculous to try to work them out entirely via macros since they differ depending on platform, architecture, and compiler all at once, so use a compiler probe instead.
This uses no more memory than before on 64 bit systems and is required to implement wide string support.
Required before wide string support can be implemented.
It'd help if the code specific to Windows would actually get used.
Originally I was planning on passing the length of strings to the CStr REPR using it, but it's impossible to know before the type is composed.
Before, they were being cast to UTF-8 strings, which breaks wide/u16/u32 strings in the process.
"type" is used to pass type names, not constants representing types.
63d2f38
to
e6b3af2
Compare
Looks like AppVeyor is unhappy with my use of Edit: I didn't need to lol |
be39a08
to
07d63b1
Compare
3869964
to
f39103b
Compare
f39103b
to
fcfaa68
Compare
Is there a reason why this isn't merged yet? Do the core devs need a poke? |
See the Rakudo pullreq for info on what this does