-
Notifications
You must be signed in to change notification settings - Fork 685
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
pallet-contracts: Fix compilation on latest nightly #2986
Conversation
Apparently they changed detection for visibility identifiers on traits, which broke more than it should. There is an issue open: rust-lang/rust#119924 The easy solution for us is to move the declaration of the global variable outside of the trait. Closes: #2960
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.
So its only important inside traits?
Since otherwise we should also change it here.
Yes only in traits AFAIK. |
As the relevant rustc dev speaking, sorry for the inconvenience, I will fix this as soon as possible when time permits. |
Apparently they changed detection for visibility identifiers on traits, which broke more than it should. There is an issue open: rust-lang/rust#119924 The easy solution for us is to move the declaration of the global variable outside of the trait. Closes: paritytech#2960 (cherry picked from commit 0e124a0)
Apparently they changed detection for visibility identifiers on traits, which broke more than it should. There is an issue open: rust-lang/rust#119924 The easy solution for us is to move the declaration of the global variable outside of the trait. Closes: paritytech#2960
Apparently they changed detection for visibility identifiers on traits, which broke more than it should. There is an issue open: rust-lang/rust#119924 The easy solution for us is to move the declaration of the global variable outside of the trait.
Closes: #2960