Files

T

Paul Berry 1d57e1b096 Extract code from dependency_grapher.dart for easier re-use elsewhere in the front end.

In the process I've made the constructors for Graph, LibraryCycleNode,
and LibraryNode public.  I don't think this should be a problem, since
these are simple data structures, so there is no harm in allowing
clients to create them.

R=sigmund@google.com

Review-Url: https://codereview.chromium.org/2617483007 .

2017-01-06 11:37:12 -08:00

lib

Extract code from dependency_grapher.dart for easier re-use elsewhere in the front end.

2017-01-06 11:37:12 -08:00

test

Create a wrapper class to handle CompilerOptions in a uniform way.

2017-01-06 10:40:45 -08:00

tool

Fix perf.dart test.

2017-01-05 12:17:06 -08:00

.analysis_options

Adjust front_end analysis options to allow supermixins.

2016-11-14 11:21:44 -08:00

BUILD.gn

Add BUILD.gn for pkg/front_end to fix the Fuchsia build

2016-11-08 15:15:07 -08:00

LICENSE

Create a README and pubspec for the front_end package.

2016-10-19 12:14:38 -07:00

pubspec.yaml

Complete merge of kernel repo into SDK.

2016-11-23 12:46:29 +01:00

README.md

Create a README and pubspec for the front_end package.

2016-10-19 12:14:38 -07:00

README.md

Front end for Dart

This package provides a low-level API for use by compiler back ends that wish to implement the Dart language. It is intended for eventual use by dev_compiler, dart2js, and the Dart VM. In addition, it will share implementation details with the analyzer package--this will be accomplished by having the analyzer package import (and re-export) parts of this package's private implementation.

End-users should use the [dartanalyzer][analyzercli] command-line tool to analyze their Dart code.

Integrators that want to write tools that analyze Dart code should use the [analyzer] package.