From ecd86d9bfcc0840e4a78831090c767cb75374890 Mon Sep 17 00:00:00 2001 From: Erik Ernst Date: Mon, 22 May 2017 15:58:19 +0200 Subject: [PATCH] Adjusted wording for "return anything from void =>" to include setters Addresses issue https://github.com/dart-lang/sdk/issues/29683. R=floitsch@google.com Review-Url: https://codereview.chromium.org/2899753002 . --- CHANGELOG.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index ef746020333..2728e6aea9c 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,9 +4,10 @@ * During a dynamic type check, `void` is not required to be `null` anymore. In practice, this makes overriding `void` functions with non-`void` functions safer. -* During static analysis, a function declared using `=>` with return type `void` - now allows the returned expression to have any type. For example, assuming the - declaration `int x;`, it is now type correct to have `void f() => ++x;`. +* During static analysis, a function or setter declared using `=>` with return + type `void` now allows the returned expression to have any type. For example, + assuming the declaration `int x;`, it is now type correct to have + `void f() => ++x;`. #### Strong Mode @@ -21,8 +22,8 @@ Packages that implement `Future` must either type the `onValue` parameter to entirely to allow inference to fill in the type. * The following is also a change in strong mode: During static analysis, a - function declared using `=>` with return type `void` now allows the returned - expression to have any type. + function or setter declared using `=>` with return type `void` now allows the + returned expression to have any type. ### Core library changes