Support new library/import syntax

Support new library/import syntax

This change simply adds new syntax support for the functionality we
currently have in the VM.

- Support for library and import, import-as.
- Still to do: show/hide combinators, export, library parts.
Committed: https://code.google.com/p/dart/source/detail?r=12216

[hausner, 2012-09-11 18:45:02]

Turns out that co19 is already using the new import syntax, so I could drop the
prefix_new_test in the language suite. It does not add test coverage, only test
runtime :)

[regis, 2012-09-11 19:11:26]

LGTM

http://codereview.chromium.org/10928121/diff/1/tests/co19/co19-runtime.status
File tests/co19/co19-runtime.status (right):

http://codereview.chromium.org/10928121/diff/1/tests/co19/co19-runtime.status...
tests/co19/co19-runtime.status:126: 
How about removing instead of commenting out?

http://codereview.chromium.org/10928121/diff/1/tests/co19/co19-runtime.status...
tests/co19/co19-runtime.status:219: 
What is the problem with the new failing tests above? I suppose it is related to
your change? You should change the failure reason.

[hausner, 2012-09-11 20:04:07]

Thank you.

http://codereview.chromium.org/10928121/diff/1/tests/co19/co19-runtime.status
File tests/co19/co19-runtime.status (right):

http://codereview.chromium.org/10928121/diff/1/tests/co19/co19-runtime.status...
tests/co19/co19-runtime.status:126: 
On 2012/09/11 19:11:26, regis wrote:
> How about removing instead of commenting out?

Done.

http://codereview.chromium.org/10928121/diff/1/tests/co19/co19-runtime.status...
tests/co19/co19-runtime.status:219: 
On 2012/09/11 19:11:26, regis wrote:
> What is the problem with the new failing tests above? I suppose it is related
to
> your change? You should change the failure reason. 
No these changes come in through the upgrade of co19, not as a result of my
change. Yes, someone will have to triage them.

[regis, 2012-09-11 20:53:08]

On 2012/09/11 20:04:07, hausner wrote:
> Thank you.
> 
> http://codereview.chromium.org/10928121/diff/1/tests/co19/co19-runtime.status
> File tests/co19/co19-runtime.status (right):
> 
>
http://codereview.chromium.org/10928121/diff/1/tests/co19/co19-runtime.status...
> tests/co19/co19-runtime.status:126: 
> On 2012/09/11 19:11:26, regis wrote:
> > How about removing instead of commenting out?
> 
> Done.
> 
>
http://codereview.chromium.org/10928121/diff/1/tests/co19/co19-runtime.status...
> tests/co19/co19-runtime.status:219: 
> On 2012/09/11 19:11:26, regis wrote:
> > What is the problem with the new failing tests above? I suppose it is
related
> to
> > your change? You should change the failure reason. 
> No these changes come in through the upgrade of co19, not as a result of my
> change. Yes, someone will have to triage them.

But your cl is not upgrading the co19 tests. I still do not understand why you
had to add these failures to your cl.