-
Notifications
You must be signed in to change notification settings - Fork 45
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
Panic when using check_for_event #313
Comments
This seems to be specific to the nightly toolchain, works fine with stable. |
I am getting the same error using the stable toolchain (stable-x86_64-pc-windows-msvc (default)). |
Sorry for the delay in replying! I've been able to reproduce this on Linux with Rust
There's also this warning during compilation:
Switching all uses of If you open a fix, I'll merge it, but it may be better to try one of the newer and more powerful libraries instead: |
I've raised #315 if anyone's available to merge. This replaces the deprecated calls with MaybeUninit. Tests all still pass and the examples now all seem to run properly. |
While looking at this I noticed there's a couple of other bits that are currently giving deprecated warnings that I'd guess will break in later versions of rust:
If wanted I can push fixes for those too. |
also points the tcod dependency to github where a fix has been merged. a new version of the crate hasn't been released yet. tomassedovic/tcod-rs#313
Hi, switching to mem::MaybeUninit doesn't seem to do much, i get the same error on both stable and nightly toolchain
Line 193: let mut c_key_state: mem::MaybeUninit<ffi::TCOD_key_t> = mem::MaybeUninit::uninit(); Why not just using an |
I'm hitting this by following the tutorial about Rogue Like. https://tomassedovic.github.io/roguelike-tutorial/part-7-gui.html (I'm putting this in case someone go through the tutorial and reach the same issue) |
For anyone that would like to finish the tutorial as exercise, switching to master branch in cargo worked for me (at least, for this specific issue).
|
Switching to master seems to solve the error, but for some odd reason, there is an occasional input stick. It's like something isn't registering a key release... |
Getting the same error |
As @giulio-Joshi said above, I fixed this by changing my
|
I tried to use the
check_for_event
function, but got this error:I am using the Rust nightly toolchain, if that's somehow related.
The text was updated successfully, but these errors were encountered: