-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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 FFI specs on release builds #12601
Fix FFI specs on release builds #12601
Conversation
Wouldn't it make sense to move that constant into the actual code in the |
|
In the specs we could just use Int64 everywhere without needing ffi_arg at all. That should promote correctly. |
In case someone else or ourselves later try to publicize |
Yes, that's exactly why I suggested to move it out of the spec into the implementation. |
@straight-shoota am I getting it right that you meant to move the code for the Sarg type to |
Yes, either that or remove it entirely (because it's only used in the spec and there we can simply just use the bigger type with Int64 and then there's no need for it). |
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.
Regardless of that, I'm fine with merging it as is - or with changes in either of the directions I suggested.
I'd like to get this fix into 1.6.1 and not hold up the release for long.
But this can be done after 1.6.1. Just don't run the specs in release mode. I think ffi has been there since 1.5.0 |
In theory we cannot take an |
I don't want to reinterpret Int64 as Int32. I just want to switch the return type to Int64 entirely. |
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.
Thank you ❤️
Should fix #12592.