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
With any luck, Rustfmt 1.0 will happen very soon. The Rust community takes promises of stability very seriously, and Rustfmt (due to being a tool as well as a library) has some interesting constraints on stability. Users should be able to update Rustfmt without hurting their workflow. Where it is used in scripts or on CI, updating Rustfmt should not cause operational errors or unexpected failure.
NEW TRACKING ISSUE = #63066 Implementation status The basic feature as specified in RFC 1522 is implemented, however there have been revisions that are still in need of work: impl Trait in argument position extend to cover traits support elision Argument-position impl Trait requires a named lifetime #49287 impl Trait in return position is basically implemented, but: filter lifetimes code accepts t
This is a sub-issue of #44662 proposing the Rust 2015 stabilization of dyn Trait. Status The decision is made, we just need a stabilization PR! Details The new syntactic form dyn <relative-path> is added. It is an error to use dyn <relative-path> if path does not name a trait. The result is a so-called dynamic trait type. For backwards compatibility, dyn can still be used as an identifier -- in ot
Fixes #33417 (tracking issue) This adds: impl From<u16> for usize impl From<i16> for isize impl From<u8> for isize … replacing corresponding TryFrom<Error=!> impls. (TryFrom still applies through the generic impl<T, U> TryFrom<U> for T where T: From<U>.) Their infallibility is supported by the C99 standard which (indirectly) requires pointers to be at least 16 bits. The remaining TryFrom impls tha
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く