Skip to content

Commit 8320e56

Browse files
committed
Minor rewording.
1 parent 416f13e commit 8320e56

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

text/0000-default-type-parameter-fallback-take-two.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ There are many motivations for this feature, the major ones are:
2424
- Allow customization in ways that most users do not care about (abstraction without cost).
2525
- Allow generalizing impls without breaking inference.
2626

27-
These were the goals of accepted [RFC 213](https://github.com/rust-lang/rfcs/blob/master/text/0213-defaulted-type-params.md). This RFC intends to bring revisit this discussion, with an extended motivation and a better specified API evolution story, so that we may get the feature back on track.
27+
These were the goals of accepted [RFC 213](https://github.com/rust-lang/rfcs/blob/master/text/0213-defaulted-type-params.md). This RFC revisits that discussion with an extended motivation and a better specified API evolution story, so that we may get the feature back on track.
2828

2929
The key concrete proposals are:
3030

@@ -284,7 +284,7 @@ The lints will guide you to add `_` where possible, the underscore represents an
284284

285285
Defaults may be set for type parameters in in traits, impls, struct and enum definitions and also methods and fns. They may not be set in `type` aliases. They also may not be set in methods and associated fns of trait impls, such defaults can only be set in the trait declaration. As per RFC 213, parameters with defaults must be trailing and may not be forward declared.
286286

287-
The behaviour of omited parameters in partially supplied parameter lists is as per RFC 213, they are inferred as if filled in with `_`. This is relevant to this [postponed RFC](https://github.com/rust-lang/rfcs/pull/1196) that suggests extending that behaviour to non-defaulted parameters.
287+
The behaviour of partially supplied parameter lists is as per RFC 213, omited parameters that have a default are inferred as if filled in with `_`. This is relevant to this [postponed RFC](https://github.com/rust-lang/rfcs/pull/1196) that suggests extending that behaviour to non-defaulted parameters.
288288

289289
## Defaults as fallbacks for inference
290290

0 commit comments

Comments
 (0)