-
Notifications
You must be signed in to change notification settings - Fork 174
Fix errors, warnings and lints on Beta #184
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
Okay, still not quite sure what the correct fix for this is, but here's the reason for the regression on the example of the failing
|
I'm just not able to read code. Of course, Due to some change in the beta compiler, the outer |
Less invasive workaround for the glob shadowing issue - rust-lang/rust#65090 (comment). |
Weird 😲 for either workaround id like a reference to the rustc issue so people aren’t confused and if it gets fixed we can go back to what it was ? |
The link in the previous comment refers to that issue - rust-lang/rust#65090. |
This is a huge change with a huge diff can we just do petrochenkovs change ? I can push it |
I just meant a link in code for the fix :) |
Uh yeah, sorry for the big diff. Contains lots of indentation. I agree that it’s a little large. If you prefer the other fix, I can change it. On a personal note, I’m not a big fan of shadowing. It does not seem too clean and can lead to situations that are hard to debug (as seen in this instance). |
Or feel free to change this PR :) Please just retain the first commit so that we get the warnings fixed, too. |
@jan-auer I have applied @petrochenkov fix but I think you need to allow me to push onto your branch? Not sure; I tried various variations on:
but my git skills probably need work. Do you know a quick command to push to your remote branch? Nothing seems to work for me: (and |
efb8d5b
to
fe0ea8c
Compare
@m4b not sure, sounds like this should have worked :) Rebased the branch now. |
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.
Ok wonderful, thanks so much!
Taking a closer look at the test failures on beta it seems like
repr(C)
is broken now on Beta. The compiler introduces additional padding aroundu32
fields that are already aligned. There were a bunch of other warnings that are now fixed in this PR, but the core problem still exists.