Files

T

Paul Berry e3347e03f7 Use a non-null TypeInferrer even in non-strong mode.

This is necessary because some of the TypeInferrer's roles (e.g. type
promotion and determination of the types of constants) are still
needed in non-strong mode.

R=ahe@google.com

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

2017-04-20 04:11:19 -07:00

lib

Use a non-null TypeInferrer even in non-strong mode.

2017-04-20 04:11:19 -07:00

test

Wrap VariableDeclarations in Blocks as specified by Kernel.

2017-04-20 09:31:36 +02:00

testcases

Add local type inference logic for integer literals.

2017-04-20 03:36:19 -07:00

tool

Move kernel baseline tests to front_end.

2017-04-19 10:57:58 +02:00

analysis_options.yaml

Move kernel baseline tests to front_end.

2017-04-19 10:57:58 +02:00

BUILD.gn

Updated build files for Fuchsia. (#29382 )

2017-04-18 15:02:19 -07:00

front_end.iml

Introduce a shadow hierarchy and factory class for use by fasta's BodyBuilder.

2017-03-24 08:25:59 -07:00

LICENSE

Create a README and pubspec for the front_end package.

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

messages.yaml

Use message.yaml in parser.

2017-03-29 11:02:23 +02:00

pubspec.yaml

analyzer and front_end alphas.

2017-01-31 14:00:16 -08: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.