Fix unintended spec change: Final fields not being initialized is only a warning.

Fix unintended spec change: Final fields not being initialized is only a warning.

A recent spec change made it an error, but the existing spec didn't actually
say that - it's one of the few warnings that do not correspond to e runtime
error.

R=eernst@google.com

Committed: https://github.com/dart-lang/sdk/commit/81f8ea0a0a7ec92306a3d5b29d888ab0adbf33ad

[Lasse Reichstein Nielsen, 2016-12-02 11:54:46]

lrn@google.com changed reviewers:
+ eernst@google.com

[eernst, 2016-12-02 14:09:46]

lgtm

https://codereview.chromium.org/2542253003/diff/1/docs/language/dartLangSpec.tex
File docs/language/dartLangSpec.tex (right):

https://codereview.chromium.org/2542253003/diff/1/docs/language/dartLangSpec....
docs/language/dartLangSpec.tex:1393: all such variables are initialized with the
\NULL{} value.
Yeah, we shouldn't have finished https://codereview.chromium.org/2399343002 so
quickly. ;-)

[Lasse Reichstein Nielsen, 2016-12-05 09:48:42]

Description was changed from

==========
Fix unintended spec change: Final fields not being initialized is only a
warning.

A recent spec change made it an error, but the existing spec didn't actually
say that - it's one of the few warnings that do not correspond to e runtime
error.
==========

to

==========
Fix unintended spec change: Final fields not being initialized is only a
warning.

A recent spec change made it an error, but the existing spec didn't actually
say that - it's one of the few warnings that do not correspond to e runtime
error.

R=eernst@google.com

Committed:
https://github.com/dart-lang/sdk/commit/81f8ea0a0a7ec92306a3d5b29d888ab0adbf33ad
==========

[Lasse Reichstein Nielsen, 2016-12-05 09:48:44]

Committed patchset #1 (id:1) manually as
81f8ea0a0a7ec92306a3d5b29d888ab0adbf33ad (presubmit successful).