Skip to content

Commit 1feb567

Browse files
authored
Update summary
1 parent f600f0c commit 1feb567

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

text/0000-implied-bounds.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
# Summary
77
[summary]: #summary
88

9-
Eliminate the need for “redundant” bounds on functions and impls where those bounds can be inferred from the input types. For example, in this simple program, the impl would no longer require a bound, because it can be inferred from the `Foo<T>` type:
9+
Eliminate the need for “redundant” bounds on functions and impls where those bounds can be inferred from the input types and other trait bounds. For example, in this simple program, the impl would no longer require a bound, because it can be inferred from the `Foo<T>` type:
1010

1111
```rust
1212
struct Foo<T: Debug> { .. }
@@ -15,7 +15,7 @@ impl<T: Debug> Foo<T> {
1515
...
1616
}
1717
```
18-
Hence, simply writing `impl<T> Foo<T> { ... }` would suffice. We currently support implied bounds for super traits, projections and lifetimes. We propose to extend this to all where clauses on traits and types, as was already discussed [here][niko].
18+
Hence, simply writing `impl<T> Foo<T> { ... }` would suffice. We currently support implied bounds for lifetime bounds, super traits and projections. We propose to extend this to all where clauses on traits and types, as was already discussed [here][niko].
1919

2020
# Motivation
2121
[motivation]: #motivation

0 commit comments

Comments
 (0)