From e810f63283b8823deb2155b638c0825da93f8f08 Mon Sep 17 00:00:00 2001 From: Eric Holk Date: Tue, 31 Aug 2021 14:17:11 -0700 Subject: [PATCH] More precise wording around temporaries --- src/expressions/block-expr.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/expressions/block-expr.md b/src/expressions/block-expr.md index 1735a5cb6..d89fcc76e 100644 --- a/src/expressions/block-expr.md +++ b/src/expressions/block-expr.md @@ -134,7 +134,9 @@ Here the resulting future will be `Send` if `Bar` is send, since `x` is defined Note that for values of types that implement `Drop`, there is an implicit use of the value at the end of its lifetime in order to run the destructor. -Besides named variables, temporary values also count. For example in `foo(&bar, baz.await)`, the value `&bar` is considered live across the `await` point. This is also true of the scrutinee of the match expression, since [the scrutinee is live for the entire match block][temporary-scopes]. +Besides named variables, temporary values also affect auto trait inference. +For example in `foo(&bar, baz.await)`, the value `&bar` is considered live across the `await` point. +This is also true of the scrutinee of the match expression, since [the scrutinee is live for the entire match block][temporary-scopes]. ## `unsafe` blocks