rust
rust copied to clipboard
rust-lang
Empowering everyone to build reliable and efficient software.
This patch makes it possible to use varargs for calling conventions, which are either based on C (efiapi) or C is based on them (sysv64 and win64). Also pinging @phlopsi,...
### Location Somewhere near slices and ranges, maybe in sliceable types as well. ### Summary Currently there doesn't seem to be any documentation on slices (both `std::slice` and the primitive...
Gating MIR inlining on non-incremental mode causes spurious codegen test failures for contributors that do not compile rustc in incremental mode. This PR stops this behaviour, to rely only on...
Kinda fixes #99426 but I guess that really might be better staying open to see if we could make it suggest `as_mut` in a structured way. Not sure how to...
### Location std::collections::VecDeque - functions like front, back, etc. https://doc.rust-lang.org/std/collections/struct.VecDeque.html ### Summary I think there's missing time complexity (big O notation) for functions as front, back, front_mut, capacity, clear, pop_back,...
This is a tracking issue for extending available ABIs for var-args functions. The feature gate for the issue is `#![feature(extended_varargs_abi_support)]`. ### About tracking issues Tracking issues are used to record...
```rust #![feature(abi_x86_interrupt)] pub extern "x86-interrupt" fn main (_a: u128) {} ``` I suspect LLVM being the culprit.
```rust #![feature(abi_x86_interrupt)] #[repr(C)] pub struct Context rustc crash.rs Segmentation fault (core dumped) ``` Interestingly, it seems like `#[repr(C)]` is load-bearing? No crash without a `repr` on the argument type. Also...
Starting to implement `ty::ConstKind::Abstract`, most of the match cases are stubbed out, some I was unsure what to add, others I didn't want to add until a more complete implementation...
