Skip to content
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

Cannot compile with Rust 1.76.0 #114

Open
rubenfiszel opened this issue Feb 8, 2024 · 7 comments · Fixed by #117
Open

Cannot compile with Rust 1.76.0 #114

rubenfiszel opened this issue Feb 8, 2024 · 7 comments · Fixed by #117

Comments

@rubenfiszel
Copy link

Works with 1.75.0, but here is the issue with 1.76.0

  --> /home/rfiszel/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rustpython-ast-0.3.0/src/impls.rs:60:1
   |
60 | static_assertions::assert_eq_size!(crate::Stmt, [u8; 160]);
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: source type: `generic::Stmt` (1216 bits)
   = note: target type: `[u8; 160]` (1280 bits)
   = note: this error originates in the macro `static_assertions::assert_eq_size` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0512]: cannot transmute between types of different sizes, or dependently-sized types
  --> /home/rfiszel/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rustpython-ast-0.3.0/src/impls.rs:62:1
   |
62 | static_assertions::assert_eq_size!(crate::Pattern, [u8; 96]);
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: source type: `generic::Pattern` (704 bits)
   = note: target type: `[u8; 96]` (768 bits)
   = note: this error originates in the macro `static_assertions::assert_eq_size` (in Nightly builds, run with -Z macro-backtrace for more info)
@rubenfiszel rubenfiszel changed the title Cannot compile with 1.76.0 Cannot compile with Rust 1.76.0 Feb 20, 2024
@olivierlemasle
Copy link

It seems it has been "fixed" in branch main by commenting out the problematic checks: cf 29c4728 (at the time where Rust 1.76.0 was still "Nightly")

@jansol
Copy link

jansol commented Mar 23, 2024

Would be nice to have a new release that includes that fix.

@bnkc
Copy link

bnkc commented Apr 6, 2024

Is there an update on when to expect a new release?

@youknowone
Copy link
Member

Sorry for inconvenience. I will release a new version.

@fanninpm
Copy link
Contributor

fanninpm commented Apr 8, 2024

Did the new release fix everyone's problem?

@bnkc
Copy link

bnkc commented Apr 8, 2024

It did. Thankyou! @youknowone @fanninpm

@Drvanon
Copy link

Drvanon commented Apr 14, 2024

Great that this got fixed! You might want to update the README though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants