You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The next release will be a breaking change to version 2.0.0 and the new minimum supported Rust version will be 1.36.0.
It should be a no-op upgrade for almost everyone, unless you are using alloc_uninitialized. This method now uses MaybeUninit instead of raw pointers (see #40 and #38). Updating code that uses the old alloc_uninitialized should mostly mean just calling https://doc.rust-lang.org/nightly/std/mem/union.MaybeUninit.html#method.as_mut_ptr to turn the MaybeUninit into a raw pointer for your calls to std::ptr::write.
There is a 2.0.0-rc1 release candidate version on crates.io now, you can use that to test the upgrade.
If there are no bugs discovered or issues raise, I'll release 2.0.0 proper on December 3rd.
The text was updated successfully, but these errors were encountered:
The next release will be a breaking change to version 2.0.0 and the new minimum supported Rust version will be 1.36.0.
It should be a no-op upgrade for almost everyone, unless you are using
alloc_uninitialized
. This method now usesMaybeUninit
instead of raw pointers (see #40 and #38). Updating code that uses the oldalloc_uninitialized
should mostly mean just calling https://doc.rust-lang.org/nightly/std/mem/union.MaybeUninit.html#method.as_mut_ptr to turn theMaybeUninit
into a raw pointer for your calls tostd::ptr::write
.There is a
2.0.0-rc1
release candidate version on crates.io now, you can use that to test the upgrade.If there are no bugs discovered or issues raise, I'll release 2.0.0 proper on December 3rd.
The text was updated successfully, but these errors were encountered: