bors 7eef946fc0 Auto merge of #99943 - compiler-errors:tuple-trait, r=jackh726 ... Implement `std::marker::Tuple`, use it in `extern "rust-call"` and `Fn`-family traits Implements rust-lang/compiler-team#537 I made a few opinionated decisions in this implementation, specifically: 1. Enforcing `extern "rust-call"` on fn items during wfcheck, 2. Enforcing this for all functions (not just ones that have bodies), 3. Gating this `Tuple` marker trait behind its own feature, instead of grouping it into (e.g.) `unboxed_closures`. Still needing to be done: 1. Enforce that `extern "rust-call"` `fn`-ptrs are well-formed only if they have 1/2 args and the second one implements `Tuple`. (Doing this would fix ICE in #66696.) 2. Deny all explicit/user `impl`s of the `Tuple` trait, kinda like `Sized`. 3. Fixing `Tuple` trait built-in impl for chalk, so that chalkification tests are un-broken. Open questions: 1. Does this need t-lang or t-libs signoff? Fixes #99820		2022-11-06 17:48:33 +00:00
..
benches	add a benchmark for slice_iter.copied().array_chunks()	2022-10-17 23:40:21 +02:00
primitive_docs	Add primitive documentation to libcore	2021-09-12 02:23:08 +00:00
src	Auto merge of #99943 - compiler-errors:tuple-trait, r=jackh726	2022-11-06 17:48:33 +00:00
tests	Format dyn Trait better in type_name intrinsic	2022-11-01 20:41:47 +00:00
Cargo.toml	Avoid use of rand::thread_rng in stdlib benchmarks	2022-05-02 00:08:21 -07:00