forked from rust-lang/rust
-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Auto merge of rust-lang#79927 - tmandry:rollup-pwn4b1v, r=tmandry
Rollup of 11 pull requests Successful merges: - rust-lang#77027 (Improve documentation for `std::{f32,f64}::mul_add`) - rust-lang#79375 (Make the kernel_copy tests more robust/concurrent.) - rust-lang#79639 (Add long explanation for E0212) - rust-lang#79698 (Add tracking issue template for library features.) - rust-lang#79809 (Dogfood `str_split_once()`) - rust-lang#79851 (Clarify the 'default is only allowed on...' error) - rust-lang#79858 (Update const-fn doc in unstable-book) - rust-lang#79860 (Clarify that String::split_at takes a byte index.) - rust-lang#79871 (Fix small typo in `wrapping_shl` documentation) - rust-lang#79896 (Make search results tab and help button focusable with keyboard) - rust-lang#79917 (Use Symbol for inline asm register class names) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
- Loading branch information
Showing
51 changed files
with
421 additions
and
307 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,63 @@ | ||
--- | ||
name: Library Tracking Issue | ||
about: A tracking issue for an unstable library feature. | ||
title: Tracking Issue for XXX | ||
labels: C-tracking-issue T-libs | ||
--- | ||
<!-- | ||
Thank you for creating a tracking issue! | ||
Tracking issues are for tracking a feature from implementation to stabilization. | ||
Make sure to include the relevant RFC for the feature if it has one. | ||
If the new feature is small, it may be fine to skip the RFC process. In that | ||
case, you can use use `issue = "none"` in your initial implementation PR. The | ||
reviewer will ask you to open a tracking issue if they agree your feature can be | ||
added without an RFC. | ||
--> | ||
|
||
Feature gate: `#![feature(...)]` | ||
|
||
This is a tracking issue for ... | ||
|
||
<!-- | ||
Include a short description of the feature. | ||
--> | ||
|
||
### Public API | ||
|
||
<!-- | ||
For most library features, it'd be useful to include a summarized version of the public API. | ||
(E.g. just the public function signatures without their doc comments or implementation.) | ||
--> | ||
|
||
```rust | ||
... | ||
``` | ||
|
||
### Steps / History | ||
|
||
<!-- | ||
In the simplest case, this is a PR implementing the feature followed by a PR | ||
that stabilises the feature. However it's not uncommon for the feature to be | ||
changed before stabilization. For larger features, the implementation could be | ||
split up in multiple steps. | ||
--> | ||
|
||
- [ ] Implementation: ... | ||
- [ ] Stabilization PR | ||
|
||
### Unresolved Questions | ||
|
||
<!-- | ||
Include any open questions that need to be answered before the feature can be | ||
stabilised. If multiple (unrelated) big questions come up, it can be a good idea | ||
to open a separate issue for each, to make it easier to keep track of the | ||
discussions. | ||
It's useful to link any relevant discussions and conclusions (whether on GitHub, | ||
Zulip, or the internals forum) here. | ||
--> | ||
|
||
- None yet. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
Cannot use the associated type of | ||
a trait with uninferred generic parameters. | ||
|
||
Erroneous code example: | ||
|
||
```compile_fail,E0212 | ||
pub trait Foo<T> { | ||
type A; | ||
fn get(&self, t: T) -> Self::A; | ||
} | ||
fn foo2<I : for<'x> Foo<&'x isize>>( | ||
field: I::A) {} // error! | ||
``` | ||
|
||
In this example, we have to instantiate `'x`, and | ||
we don't know what lifetime to instantiate it with. | ||
To fix this, spell out the precise lifetimes involved. | ||
Example: | ||
|
||
``` | ||
pub trait Foo<T> { | ||
type A; | ||
fn get(&self, t: T) -> Self::A; | ||
} | ||
fn foo3<I : for<'x> Foo<&'x isize>>( | ||
x: <I as Foo<&isize>>::A) {} // ok! | ||
fn foo4<'a, I : for<'x> Foo<&'x isize>>( | ||
x: <I as Foo<&'a isize>>::A) {} // ok! | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.