Implement all x86 vendor intrinsics · Issue #40 · rust-lang/stdarch
This is intended to be a tracking issue for implementing all vendor intrinsics in this repository. This issue is also intended to be a guide for documenting the process of adding new vendor intrinsics to this crate. If you decide to implement a set of vendor intrinsics, please check the list below to make sure somebody else isn't already working on them. If it's not checked off or has a name next
Add support for the Visual Studio 2017 linker · Issue #38584 · rust-lang/rust
With Visual Studio 2017, Microsoft has changed the folder structure it uses for everything. link.exe is now located at C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.10.24728\bin\HostX64\x64\link.exe. As you can see, the folder is dependent on the actual edition of Visual Studio as well. Currently, Rust does not seem to recognize this path correctly. I don’t know e
rfcs/text/2033-experimental-coroutines.md at master · rust-lang/rfcs
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
Tracking issue for allocation APIs · Issue #27700 · rust-lang/rust
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
Tracking issue for location of facade crates · Issue #27783 · rust-lang/rust
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
Tracking issue for changing the global, default allocator (RFC 1974) · Issue #27389 · rust-lang/rust
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Tracking issue for `log_syntax`, `trace_macros` · Issue #29598 · rust-lang/rust
GitHub - rust-lang/chalk: An implementation and definition of the Rust trait system using a PROLOG-like logic solver
rfcs/text/2071-impl-trait-type-alias.md at master · rust-lang/rfcs
Impl Try for Option by huntiep · Pull Request #42526 · rust-lang/rust
Initial support for `..=` syntax by Badel2 · Pull Request #44709 · rust-lang/rust
rfcs/text/2094-nll.md at master · rust-lang/rfcs
Add generic_assert by ishitatsuyuki · Pull Request #2011 · rust-lang/rfcs
Stop relying on rpath · Issue #11747 · rust-lang/rust
cdylib on Windows provides only the .dll without the associated .lib import library · Issue #3934 · rust-lang/cargo
GitHub - rust-lang/rust-bindgen: Automatically generates Rust FFI bindings to C (and some C++) libraries.
RFC: numerics reform by aturon · Pull Request #369 · rust-lang/rfcs
staticlib is ridiculously large. · Issue #24764 · rust-lang/rust
Post-build script execution · Issue #545 · rust-lang/cargo
Better support for --emit · Issue #2342 · rust-lang/cargo
