-
Notifications
You must be signed in to change notification settings - Fork 783
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
offset_of!
not stable in Rust v1.63.0
#4408
Comments
This only uses the offset of macro from the memoffset crate as far as I can
tell.
…On Thu, Aug 1, 2024, 3:20 PM Marc Pabst ***@***.***> wrote:
Bug Description
I think #4254 <#4254> introduced usage
of the offset_of! macro which is not available in the current MSRV.
Steps to Reproduce
Build with v1.63.0
Backtrace
*No response*
Your operating system and version
n/a
Your Python version (python --version)
n/a
Your Rust version (rustc --version)
< 1.77.0
Your PyO3 version
0.22.2
How did you install python? Did you use a virtualenv?
n/a
Additional Info
*No response*
—
Reply to this email directly, view it on GitHub
<#4408>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAGBDLWCO3EO2P6DD2653ZPKC6FAVCNFSM6AAAAABL3FW6ZOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ2DGMRTGA2DMNQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I'm seing a
|
Try running Also your error is from a PyO3 0.21 source file so predates #4254 |
Yeah, looks like it's my messed-up local toolchain which reports as a newer version than what it actually is. I suspect that in turn confuses |
Bug Description
I think #4254 introduced usage of the
offset_of!
macro which is not available in the current MSRV.Steps to Reproduce
Build with v1.63.0
Backtrace
No response
Your operating system and version
n/a
Your Python version (
python --version
)n/a
Your Rust version (
rustc --version
)< 1.77.0
Your PyO3 version
0.22.2
How did you install python? Did you use a virtualenv?
n/a
Additional Info
No response
The text was updated successfully, but these errors were encountered: