Motivation The reasons I'm aware of are: Large interest, see Add cargo-add (from cargo-edit) to cargo proper #5586 Make it easier to add a dependency when you don't care about the version (instead of having to find it or just using the major version if thats all you remember) Provide a guided experience, including Catch or prevent errors earlier in the process Bring the Manifest format documentati
Feature gate: #![feature(strict_provenance)] read the docs get the stable polyfill subtasks This is a tracking issue for the strict_provenance feature. This is a standard library feature that governs the following APIs: pointer::addr pointer::with_addr pointer::map_addr core::ptr::invalid core::ptr::invalid_mut IMPORTANT: This is purely a set of library APIs to make your code more clear/reliable,
error reporting in constants prints a stacktrace through all called const fns Trivial constant propagation and folding in MIR (always active, irrelevant of the optimization level) can now use floating constants in patterns (previously only floating point literals were allowed) the future compat lint is still produced for both cases can index into constant arrays during const eval (previously featu
Extend Rust's borrow system to support non-lexical lifetimes -- these are lifetimes that are based on the control-flow graph, rather than lexical scopes. The RFC describes in detail how to infer these new, more flexible regions, and also describes how to adjust our error messages. The RFC also describes a few other extensions to the borrow checker, the total effect of which is to eliminate many co
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く