Remove code that requires whole-program compile

Remove code that requires whole-program compile

This change removes functionality that is not part of the core Dart Dev
Compiler, in particular those features that were not designed for
incremental/modular compilation.

For a while, the primary way to use DDC will be as a compiler invoked by
a build system, e.g. make or bazel or some node.js based-build system.

We'd love to see the user functionality provided by these return.
In particular, a well designed server+watcher system would be a huge
boost to productivity!

I'll see about moving over HTML reporting to Analyzer CLI. It has a lovely UI.
Thanks to everyone who contributed these features.

The following features were removed:

* DDC transformer. Transformers require whole world, in memory files.
* DDC server. The server has its own mini-build system.
* Various kinds of reporting. These should be moved to Analyzer CLI.

Note: batch compiler and the node runner are left for now.

R=vsm@google.com

Committed: https://github.com/dart-lang/dev_compiler/commit/d230731ec991652fbee64fa217333c06150d4026

[Jennifer Messerly, 2016-03-12 01:28:48]

Description was changed from

==========
Remove code that requires whole-program compile

This change removes functionality that is not part of the core Dart Dev
Compiler, in particular those features that were not designed for
incremental/modular compilation. We would greatly like to see the user
functionality of these return, in a faster/better form in the future.

The following features were removed:

* DDC transformer. Transformers require whole world, in memory files.
* DDC server. The server has its own mini-build system.
* Various kinds of reporting. These should be moved to Analyzer CLI.

Note: batch compiler itself as well as the V8 runner are somewhat
problematic as well. Those are left for now to address in a follow up.
==========

to

==========
Remove code that requires whole-program compile

This change removes functionality that is not part of the core Dart Dev
Compiler, in particular those features that were not designed for
incremental/modular compilation. We would greatly like to see the user
functionality of these return, in a faster/better form in the future.

The following features were removed:

* DDC transformer. Transformers require whole world, in memory files.
* DDC server. The server has its own mini-build system.
* Various kinds of reporting. These should be moved to Analyzer CLI.

Note: batch compiler and the node runner are left for now.
==========

[Jennifer Messerly, 2016-03-12 01:28:49]

jmesserly@google.com changed reviewers:
+ vsm@google.com

[Jennifer Messerly, 2016-03-12 01:33:20]

Description was changed from

==========
Remove code that requires whole-program compile

This change removes functionality that is not part of the core Dart Dev
Compiler, in particular those features that were not designed for
incremental/modular compilation. We would greatly like to see the user
functionality of these return, in a faster/better form in the future.

The following features were removed:

* DDC transformer. Transformers require whole world, in memory files.
* DDC server. The server has its own mini-build system.
* Various kinds of reporting. These should be moved to Analyzer CLI.

Note: batch compiler and the node runner are left for now.
==========

to

==========
Remove code that requires whole-program compile

This change removes functionality that is not part of the core Dart Dev
Compiler, in particular those features that were not designed for
incremental/modular compilation.

For a while, the primary way to use DDC will be as a compiler invoked by
a build system, e.g. make or bazel or some node.js based-build system.

We'd love to see the user functionality provided by these return.
In particular, a well designed server+watcher system would be a huge
boost to productivity!

I'll see about moving over HTML reporting to Analyzer CLI. It has a lovely UI.
Thanks to everyone who contributed these features.

The following features were removed:

* DDC transformer. Transformers require whole world, in memory files.
* DDC server. The server has its own mini-build system.
* Various kinds of reporting. These should be moved to Analyzer CLI.

Note: batch compiler and the node runner are left for now.
==========

[Jennifer Messerly, 2016-03-12 01:36:09]

@Vijay, this is the follow up to your message:
https://groups.google.com/a/dartlang.org/d/msg/dev-compiler/M82d7MphW8M/7Z2Ou...

[Jennifer Messerly, 2016-03-12 01:37:36]

https://codereview.chromium.org/1788973002/diff/1/lib/src/codegen/reify_coerc...
File lib/src/codegen/reify_coercions.dart (right):

https://codereview.chromium.org/1788973002/diff/1/lib/src/codegen/reify_coerc...
lib/src/codegen/reify_coercions.dart:64: // TODO(jmesserly): what is going on
here? We are dropping these typedefs
Note, I actually fixed this TODO already in:
https://codereview.chromium.org/1783603009/

I will remove the TODO when merging it.

[vsm, 2016-03-14 14:39:16]

lgtm

Let's publish a new DDC before landing this.  This may break some Angular work,
but I think we can rebuild what we need before pushing the next DDC.

[ochafik, 2016-03-14 15:44:51]

ochafik@google.com changed reviewers:
+ ochafik@google.com

[ochafik, 2016-03-14 15:44:51]

Hey John, re/ the transformer, my plan was to make it incremental as soon as
possible (i.e. have it output summaries per libraries, etc), although I
understand the temp removal if there's api breakages (it currently uses the
BatchCompiler that is still around though, right?).

Also, would be nice to reintroduce some e2e test soon after this CL :-)

Cheers

[Jennifer Messerly, 2016-03-14 22:40:45]

On 2016/03/14 15:44:51, ochafik wrote:
> Hey John, re/ the transformer, my plan was to make it incremental as soon as
> possible (i.e. have it output summaries per libraries, etc), although I
> understand the temp removal if there's api breakages (it currently uses the
> BatchCompiler that is still around though, right?).
> 
> Also, would be nice to reintroduce some e2e test soon after this CL :-)
> 
> Cheers

> Hey John, re/ the transformer, my plan was to make it incremental as soon as
> possible (i.e. have it output summaries per libraries, etc), although I
> understand the temp removal if there's api breakages (it currently uses the
> BatchCompiler that is still around though, right?).

Yeah, to help the transition, we made need to have something that takes a set of
Dart entry points and computes the build graph, before handing it off to the
incremental/modular compile.

Note the automatic computation/evaluation of build graph is probably not
something we want long term in the compiler. We need to get folks in the habit
of using a build system, like Bazel. I'm going to see how far along the new Dart
build system is, perhaps that lets us skip it entirely.

FWIW, I believe the new "build" replaces transformers. It's sort of like
transformers were V1, this is V2.

> Also, would be nice to reintroduce some e2e test soon after this CL :-)

Yup, testing command line build & verify output works in a browser would be
good. :)

[vsm, 2016-03-15 17:38:48]

On 2016/03/14 22:40:45, John Messerly wrote:
> On 2016/03/14 15:44:51, ochafik wrote:
> > Hey John, re/ the transformer, my plan was to make it incremental as soon as
> > possible (i.e. have it output summaries per libraries, etc), although I
> > understand the temp removal if there's api breakages (it currently uses the
> > BatchCompiler that is still around though, right?).
> > 
> > Also, would be nice to reintroduce some e2e test soon after this CL :-)
> > 
> > Cheers
> 
> > Hey John, re/ the transformer, my plan was to make it incremental as soon as
> > possible (i.e. have it output summaries per libraries, etc), although I
> > understand the temp removal if there's api breakages (it currently uses the
> > BatchCompiler that is still around though, right?).
> 
> Yeah, to help the transition, we made need to have something that takes a set
of
> Dart entry points and computes the build graph, before handing it off to the
> incremental/modular compile.
> 
> Note the automatic computation/evaluation of build graph is probably not
> something we want long term in the compiler. We need to get folks in the habit
> of using a build system, like Bazel. I'm going to see how far along the new
Dart
> build system is, perhaps that lets us skip it entirely.
> 
> FWIW, I believe the new "build" replaces transformers. It's sort of like
> transformers were V1, this is V2.
> 
> > Also, would be nice to reintroduce some e2e test soon after this CL :-)
> 
> Yup, testing command line build & verify output works in a browser would be
> good. :)

I've published a DDC with the latest fixes (up to this :-)).

[Jennifer Messerly, 2016-03-15 18:30:53]

Description was changed from

==========
Remove code that requires whole-program compile

This change removes functionality that is not part of the core Dart Dev
Compiler, in particular those features that were not designed for
incremental/modular compilation.

For a while, the primary way to use DDC will be as a compiler invoked by
a build system, e.g. make or bazel or some node.js based-build system.

We'd love to see the user functionality provided by these return.
In particular, a well designed server+watcher system would be a huge
boost to productivity!

I'll see about moving over HTML reporting to Analyzer CLI. It has a lovely UI.
Thanks to everyone who contributed these features.

The following features were removed:

* DDC transformer. Transformers require whole world, in memory files.
* DDC server. The server has its own mini-build system.
* Various kinds of reporting. These should be moved to Analyzer CLI.

Note: batch compiler and the node runner are left for now.
==========

to

==========
Remove code that requires whole-program compile

This change removes functionality that is not part of the core Dart Dev
Compiler, in particular those features that were not designed for
incremental/modular compilation.

For a while, the primary way to use DDC will be as a compiler invoked by
a build system, e.g. make or bazel or some node.js based-build system.

We'd love to see the user functionality provided by these return.
In particular, a well designed server+watcher system would be a huge
boost to productivity!

I'll see about moving over HTML reporting to Analyzer CLI. It has a lovely UI.
Thanks to everyone who contributed these features.

The following features were removed:

* DDC transformer. Transformers require whole world, in memory files.
* DDC server. The server has its own mini-build system.
* Various kinds of reporting. These should be moved to Analyzer CLI.

Note: batch compiler and the node runner are left for now.

R=vsm@google.com

Committed:
https://github.com/dart-lang/dev_compiler/commit/d230731ec991652fbee64fa21733...
==========

[Jennifer Messerly, 2016-03-15 18:30:55]

Committed patchset #2 (id:20001) manually as
d230731ec991652fbee64fa217333c06150d4026 (presubmit successful).