Skip to content

Commit 8f641ec

Browse files
committed
Clarify that use<..> appears before any bounds
The `use<..>` syntax is not part of any bound and must appear before all bounds. Let's say this a bit more clearly in one place.
1 parent ee785c8 commit 8f641ec

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

text/3617-precise-capturing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ We need some way to migrate this kind of code.
6262
# Guide-level explanation
6363
[guide-level-explanation]: #guide-level-explanation
6464

65-
In all editions, RPIT-like `impl Trait` opaque types may include `use<..>` in the bound to specify which in-scope generic parameters are captured or that no in-scope generic parameters are captured (with `use<>`). If `use<..>` is provided, it entirely overrides the implicit rules for which generic parameters are captured.
65+
In all editions, RPIT-like `impl Trait` opaque types may include `use<..>` before any bounds to specify which in-scope generic parameters are captured or that no in-scope generic parameters are captured (with `use<>`). If `use<..>` is provided, it entirely overrides the implicit rules for which generic parameters are captured.
6666

6767
One way to think about `use<..>` is that, in Rust `use` brings things *into scope*, and here we are bringing certain generic parameters into scope for the hidden type.
6868

0 commit comments

Comments
 (0)