CLI. Always fully parse given target files.

CLI. Always fully parse given target files.

It seems that we have a bug - when we analyze a SDK library during
running shared tests, we still parse it dietly so we don't actually
validate that bodies are warning-free.

And when we attempt to use SDK summary, we again parse a library
dietly, but then attempt to apply the full summary using
DeclarationResolver, which fails because we fail to bind some elements
to not parsed nodes.

R=brianwilkerson@google.com
BUG=

Committed: https://github.com/dart-lang/sdk/commit/09672f09c6b70f3de798201bccc77e5046a4b04f

[Brian Wilkerson, 2016-02-12 14:48:01]

LGTM

[scheglov, 2016-02-12 15:02:47]

Description was changed from

==========
CLI. Always fully parse given target files.

It seems that we have a bug - when we analyze a SDK library during
running shared tests, we still parse it dietly so we don't actually
validate that bodies are warning-free.

And when we attempt to use SDK summary, we again parse a library
dietly, but then attempt to apply the full summary using
DeclarationResolver, which fails because we fail to bind some elements
to not parsed nodes.

R=brianwilkerson@google.com
BUG=
==========

to

==========
CLI. Always fully parse given target files.

It seems that we have a bug - when we analyze a SDK library during
running shared tests, we still parse it dietly so we don't actually
validate that bodies are warning-free.

And when we attempt to use SDK summary, we again parse a library
dietly, but then attempt to apply the full summary using
DeclarationResolver, which fails because we fail to bind some elements
to not parsed nodes.

R=brianwilkerson@google.com
BUG=

Committed:
https://github.com/dart-lang/sdk/commit/09672f09c6b70f3de798201bccc77e5046a4b04f
==========

[scheglov, 2016-02-12 15:02:48]

Committed patchset #1 (id:1) manually as
09672f09c6b70f3de798201bccc77e5046a4b04f (presubmit successful).