RFC for `if let` expression by lilyball · Pull Request #160 · rust-lang/rfcs
Start Date: (fill me in with today's date, YYYY-MM-DD) RFC PR #: (leave this empty) Rust Issue #: (leave this empty) Summary Introduce a new if let PAT = EXPR { BODY } construct. This allows for refutable pattern matching without the syntactic and semantic overhead of a full match, and without the corresponding extra rightward drift. Informally this is known as an "if-let statement". Motivation Ma
rfcs/text/0160-if-let.md at master · rust-lang/rfcs
Many times in the past, people have proposed various mechanisms for doing a refutable let-binding. None of them went anywhere, largely because the syntax wasn't great, or because the suggestion introduced runtime failure if the pattern match failed. This proposal ties the refutable pattern match to the pre-existing conditional construct (i.e. if statement), which provides a clear and intuitive exp
package namespaces · Issue #2514 · rust-lang/cargo
Hello, Probably everyone has already heard about the recent issue with NPM and 'kik' package. That story could possibly occur with many other package repositories as well. Cargo is in this list. Though there's no such problem in Cargo like accidental code removal and/or replacement with some other vulnerable code, but the naming conflict can possibly occur. We live in the world of copyright and tr
rfcs/text/2504-fix-error.md at master · rust-lang/rfcs
The Error trait has long been known to be flawed in several respects. In particular: The required description method is limited, usually, to returning static strings, and has little utility that isn't adequately served by the required Display impl for the error type. The signature of the cause method does not allow the user to downcast the cause type, limiting the utility of that method unnecessar
rfcs/2394-async_await.md at master · rust-lang/rfcs · GitHub
High performance network services frequently use asynchronous IO, rather than blocking IO, because it can be easier to get optimal performance when handling many concurrent connections. Rust has seen some adoption in the network services space, and we wish to continue to enable those users - and to enable adoption by other users - by making it more ergonomic to write asynchronous network services
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
failed to authenticate when downloading repository · Issue #3381 · rust-lang/cargo
clippy and rls components are not available since nightly-2019-02-09 · Issue #3749 · rust-lang/rust-clippy
Implement Unsized Rvalues by qnighy · Pull Request #51131 · rust-lang/rust
Stabilize dbg!(...) by Centril · Pull Request #56395 · rust-lang/rust
GitHub - rust-lang/rust-clippy: A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
rfcs/text/1644-default-and-expanded-rustc-errors.md at master · rust-lang/rfcs
Removed 'proc' from the reserved keywords list by zesterer · Pull Request #49699 · rust-lang/rust · GitHub
Projects that use crates.io's API · rust-lang/crates.io Wiki · GitHub
Simpler alternative dbg!() macro by SimonSapin · Pull Request #2361 · rust-lang/rfcs
rfcs/text/2071-impl-trait-existential-types.md at master · rust-lang/rfcs
rfcs/text/2361-dbg-macro.md at master · rust-lang/rfcs
Add target thumbv7a-pc-windows-msvc by jordanrh1 · Pull Request #53621 · rust-lang/rust
GitHub - rust-lang/rust-central-station: Old home of some infra pieces
GitHub - rust-lang/rust-marketing: Rust marketing handbook
RFC: Rust 2018 Roadmap by aturon · Pull Request #2314 · rust-lang/rfcs
