io_safety has to do with the APIs for manually messing with file descriptors or handles, and it was stabilized recently
#error, use of unstable library feature 'io_safety'
verbal vector
Update your compiler
Run rustup update, IIRC
radiant plume
it sounds like that library is nightly only
verbal vector
You might need to update and install a nightly, I guess?
Which is, uh, rustup update +nightly? I don't actually know the rustup CLI well
radiant plume
right. rust #![feature( maybe_uninit_uninit_array, maybe_uninit_slice, once_cell, linked_list_cursors, generic_associated_types, min_specialization )] so this library is nightly only
i'd also like to add that min_specialization is not all that polished and absolutely not production ready, so please don't use this for anything serious
verbal vector
The first two could be done with transmute, the third with a crate, the fourth... someone is using std::collections::LinkedList? The fifth will be stable soon, but min_specialization is not ready, nowhere near
radiant plume
yeah i think the other features are fine. linked_list is kinda weird but fine
I would consider making an issue and propose making it work on stable. the first four features you can gut out and replace with stable apis/crates fairly easily. generic associated types is getting stabilized so you need only to wait. getting rid of min_specialization could be difficult depending on what they're using it for
and, uh i dont really do anything with dlls or windows dev so no idea
is it actually using the nightly?
what does rustc --version say
you can pin your project to a particular nightly with a rust-toolchain.toml file, e.g. toml [toolchain] channel = "nightly-2022-08-30" components = [ "rustfmt", "clippy" ] profile = "minimal"
i'd recommend adding one
and btw the once_cell api got renamed a while back, so you might need to figure out a particular nightly version that works
if you add this file it will use that toolchain automatically
