-
Notifications
You must be signed in to change notification settings - Fork 259
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
Failed to install in rust 1.61.0-beta.4 #708
Comments
Hmmm, this seems more like a bug with Rust beta (I don't think an update like that should be causing something that used to properly infer to fail...), but I can add an additional type annotation if it's actually needed. Generally I build/deploy with stable in mind, though. |
Did some digging, related issue: rust-lang/rust#96074 Seems like it's an issue with Rust beta. I'm marking this as an upstream issue for now, and I'll close it as the linked issue progresses, or address it based on what actions result from the issue. |
See my comments in rust-lang/rust#96074 (comment) — Regardless of the Rust change, I think you should remove the |
Yep, sounds good. |
For context, see: - #708 - rust-lang/rust#96074 This changes the calls from `as_ref()`, which was causing problems, to just `as_slice()` which works fine.
For context, see: - #708 - rust-lang/rust#96074 This changes the calls from `as_ref()`, which was causing type inference issues, to just `as_slice()` which works fine.
For context, see: - #708 - rust-lang/rust#96074 This changes the calls from `as_ref()`, which was causing type inference issues, to just `as_slice()` which works fine.
For context, see: - #708 - rust-lang/rust#96074 This changes the calls from `as_ref()`, which was causing type inference issues, to just `as_slice()` which works fine.
For context, see: - #708 - rust-lang/rust#96074 This changes the calls from `as_ref()`, which was causing type inference issues, to just `as_slice()` which works fine.
This changes various as_ref() calls as needed in order for bottom to successfully build in Rust beta 1.61, as they were causing type inference issues. These calls were either removed or changed to an alternative that does build (e.g. as_slice()). Functionally, there should be no change. For context, see: - #708 - rust-lang/rust#96074
Fix has been pushed in #711 and tested to build successfully on beta for Win/Linux/macOS. |
Before you report, please take a look at Troubleshooting to see if there's already an answer to your problem. Also check out existing issues and known problems to see if your problem is already reported/known/fixed.
Also, please fill in all fields if possible - if the issue is too hard to reproduce or vague, it may not be fixed!
Describe the bug
Tried to install using
cargo install bottom --locked
. Type inference failure in Rust.Give a high level description of the bug.
What operating system/architecture are you using?
Darwin/Intel x86-64
Please mention what operating system, version, and architecture you're experiencing the problem on (ex: macOS 10.13, x86_64). Please also ensure that your system is on the list of supported systems - bug reports on unsupported systems are likely to be closed.
What terminal are you using
bottom
on?Please mention what terminal/terminal emulator you are using
bottom
on (ex: Konsole, Kitty), as well as their version and any relevant settings.What version are you on?
The latest
Please mention which version of bottom you're running (
btm -V
, nightly, etc.)!How did you install
bottom
?cargo install bottom --locked
rustc 1.61.0-beta.4 (69a6d12e9 2022-04-25)
Please mention how you installed
bottom
. If you manually compiled it, please also mention your Rust version.How can we reproduce this?
Install latest beta toolchain (
rustup update beta
)cargo install bottom --locked
Provide detailed steps on how to reproduce your problem, to the best of your ability. Be as detailed as possible. Include config files or flags if relevant. If maintainers cannot reproduce the bug, it will be very hard to fix it.
What is the actual behaviour?
What is the actual result of the given steps? Be detailed. Please include screenshots if relevant and possible.
What is the expected behaviour?
What do you believe the expected behaviour should be given these steps?
The text was updated successfully, but these errors were encountered: