Get up to speed quickly on newcomer Rust, designed to create fast, system-level software. Related video: Developing safer software with Rust Rust 1.71.1 also addressed several regressions introduced in Rust 1.71.0, including Bash completion being broken for users of the Rustup toolchain installer. Rust 1.72.0 follows Rust 1.71.1 from August 3, which fixed a situation in which the Cargo package manager was not respecting the unmask when extracting dependencies, which could have enabled a local attacker to edit the cache of extracted source code of another user. Rust 1.75 is slated to be the last Rust version to officially support Windows 7, Windows 8, and Windows 8.1. In a future release, the Rust development team plans to increase the minimum-supported Windows version to Windows 10. And a number of APIs have been stabilized including CStr::from_bytes_with_nul and CStr::to_Bytes. Developers now can do an unlimited amount of const evaluation at compile time.Įlsewhere in Rust 1.72.0, several lints from Clippy have been pulled into rustc. Rust previously limited the maximum number of statements run as a part of any given constant evaluation, to prevent user-provided const evaluation from getting into a compile-time infinite loop or otherwise taking unbounded time at compile. It could report, for example, if a function a developer tried to call is unavailable because a crate feature must be enabled.Īlso in Rust 1.72.0, const evaluation time now is unlimited. ![]() With Rust 1.72.0, the compiler will remember the name and cfg conditions of those items. Previously, items disabled like this effectively would be invisible to the compiler. The new features in Rust 1.72.0Īnnounced August 24, Rust 1.72.0 lets developers conditionally enable code using the cfg operator, for configuration conditional checks, to provide certain functions only with certain crate features or only on particular platforms. Rust 1.73 also stabilizes a number of APIs. The new methods make common code more concise and avoid running extra initialization code for the default value specified in thread_local! for new threads. ![]() ![]() LocalKey is the type of thread_local! statics. LocalKey> and LocalKey> now can be directly manipulated with get(), set(), and replace() methods instead of jumping through a with(|inner| …) closure as needed for general LocalKey work. Rust 1.73.0 also features thread local initialization.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |