サクサク読めて、アプリ限定の機能も多数！
トップへ戻る
WWDC25
github.com/rust-lang
Rust Style Guide Motivation - why use a formatting tool? Formatting code is a mostly mechanical task which takes both time and mental effort. By using an automatic formatting tool, a programmer is relieved of this task and can concentrate on more important things. Furthermore, by sticking to an established style guide (such as this one), programmers don't need to formulate ad hoc style rules, nor
github.com/rust-lang-nursery
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
Prior to this commit, packages beginning with rust or ending with rs were renamed automatically when created, unless they were binaries. The ostensible purpose of this code was to avoid people uploading "redundant" names to crates.io, which is a repository of Rust packages. This behavior was overly opinionated. It is not cargo's responsibility to discourage users from naming their packages any par
The following submodules have been updated for a new version of LLVM: src/llvm src/libcompiler_builtins - transitively contains compiler-rt src/dlmalloc This also updates the docker container for dist-i686-freebsd as the old 16.04 container is no longer capable of building LLVM. The compiler-rt/compiler-builtins and dlmalloc updates are pretty routine without much interesting happening, but the LL
The time has come again, LLVM is releasing 5.0 soon and Rust wants to / needs to follow. I have started work on the upgrade in these branches: rust-lang/rust: https://github.com/alexcrichton/rust/tree/llvm50 rust-lang/llvm: https://github.com/rust-lang/llvm/tree/rust-llvm-2017-07-20 rust-lang/compiler-rt: https://github.com/rust-lang/compiler-rt/tree/rust-2017-07-20 rust-lang-nursery/compiler-buil
One of Rust's 2017 roadmap goals is "Rust should be well-equipped for writing robust, high-scale servers". A recent survey has shown that the biggest blocker to robust, high-scale servers is ergonomic usage of async I/O (futures/Tokio/etc). Namely, the lack of async/await syntax. Syntax like async/await is essentially the defacto standard nowadays when working with async I/O, especially in languag
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
Current status Final incarnation of std::heap is being proposed in rust-lang/rfcs#1974, hopefully for stabilization thereafter. Open questions for stabilization are: Is it required to deallocate with the exact size that you allocate with? With the usable_size business we may wish to allow, for example, that you if you allocate with (size, align) you must deallocate with a size somewhere in the ran
We probably don't want to indefinitely have a large number of facade crates which are all unstable, so we should eventually stabilize these crates, fold them back into the standard library, or find a good middle ground in which they can all reside. The current set of crates considered under this issue are: rustc_unicode libc collections alloc rand Update 2018-04-05: libc and rand have moved to cra
次のページ
このページを最初にブックマークしてみませんか？
『The Rust Programming Language』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
