Files

T

Dan Rubel 874f9d0bdf Refactor for statement parsing

This CL introduces 2 new parser listener events
in preparation for parsing for control flow structures
in literal lists, sets, and maps.

Change-Id: I230f36cded714a13e4badb401fe5b5906c93a2da
Reviewed-on: https://dart-review.googlesource.com/c/91144
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
Commit-Queue: Dan Rubel <danrubel@google.com>

2019-01-25 18:15:00 +00:00

benchmarks/ikg

…

lib/src

Refactor for statement parsing

2019-01-25 18:15:00 +00:00

test

Update parser to support simple if/else control flow in literal lists, sets, and maps

2019-01-24 22:22:50 +00:00

testcases

Prevent serialization of synthetic kernel nodes

2019-01-24 18:55:44 +00:00

tool

Improve input path handling and remove extra schemas.

2019-01-16 10:17:03 +00:00

analysis_options.yaml

Stop using external deprecated members in front_end

2019-01-15 18:55:10 +00:00

error_recovery.yaml

…

LICENSE

…

messages.status

[frontend] report transformation error messages through library loader

2019-01-23 10:39:07 +00:00

messages.yaml

[frontend] report transformation error messages through library loader

2019-01-23 10:39:07 +00:00

pubspec.yaml

Prepare to publish analyzer version 0.34.2.

2019-01-16 16:44:43 +00:00

README.md

…

testing.json

[kernel] Start setting up test suite for round-trip serialization

2019-01-04 16:05:26 +00: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.

Note: The APIs in this package are in an early state; developers should be careful about depending on this package. In particular, there is no semver contract for release versions of this package. Please depend directly on individual versions.