Files

T

Jens Johansen 50836c171e [parser] Fix parsing of empty index in cascade

Fixes #42267

Change-Id: Ia09fd9e564bc0b04cdd99d3aac5093a12ab10d96
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/150926
Reviewed-by: Johnni Winther <johnniwinther@google.com>
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
Commit-Queue: Jens Johansen <jensj@google.com>

2020-06-12 06:36:58 +00:00

benchmarks/ikg

…

lib/src

Don't legacy-erase type literals.

2020-06-11 13:28:49 +00:00

parser_testcases

[parser] Fix parsing of empty index in cascade

2020-06-12 06:36:58 +00:00

test

Avoid divisive terms

2020-06-10 14:23:57 +00:00

testcases

Don't legacy-erase type literals.

2020-06-11 13:28:49 +00:00

tool

Use terms which are not divisive

2020-06-10 11:04:37 +00:00

analysis_options_no_lints.yaml

[cfe] Add predicates to detect late lowered fields.

2020-05-19 08:55:20 +00:00

analysis_options.yaml

[CFE] First batch of fixes for requiring explicit types

2019-08-15 13:13:20 +00:00

error_recovery.yaml

…

LICENSE

…

messages.status

[CFE] Error when strong mode mixed with non-opted-in

2020-05-14 17:10:51 +00:00

messages.yaml

[cfe] Provide better context in verifier's diagnostics

2020-05-26 10:02:05 +00:00

PRESUBMIT.py

[CFE] Add PRESUBMIT.py that runs a little smoke testing

2019-08-16 12:28:07 +00:00

pubspec.yaml

Prepare to publish analyzer 0.39.5

2020-04-03 17:28:47 +00:00

README.md

…

testing_with_lints.json

[kernel] Add DartType.toTypeText and Constant.toConstantText

2020-05-18 11:48:20 +00:00

testing.json

[CFE] Add _fe_analyzer_shared to CFE's 'analyze' test

2020-06-09 06:28:37 +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.