Introduced December 15, 2022, Rust 1.66 enables enums with integer representations to now use explicit discriminants, even when they have fields. This vulnerability was tracked at cve.org, with more information in the advisory. Note: Rust 1.66.1 stable, released January 10, fixed a situation in which the Cargo package manager was not verifying SSH host keys when cloning dependencies or registry indexes with SSH. And invalid literals no longer are an error under cfg(FALSE). A number of other APIs are now stable in const contexts including char::from_u32, char::from_digit, and char::to_digit. Rust 1.67 stabilizes several APIs such as ::ilog, and NonZero*::BITS. The release contains no API changes but the new implementation fixes bugs and improves performance and maintainability of the implementation. With Rust 1.67, the implementation has been switched out to be based on crossbeam-channel. Rust’s standard library has had a multi-producer, single-consumer channel since before version 1.0. In Rust 1.67, the compiler now will warn if the output is not used.Īlso in Rust 1.67, the implementation of the multi-producer, single-consumer channel of the standard library has been updated. Previously there was no way to indicate that the output of the Future is itself significant and should be used in some way. The Future trait already is annotated with #, so types implementing are automatically #. In Rust, async functions annotated with # now apply that attribute to the output of the returned impl Future. Rust 1.67, unveiled January 26, adds a compiler warning pertaining to # and async fn.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |