dart-sdk/pkg/front_end
Paul Berry b8eede8c9f Flow analysis: make propertyGet's wholeExpression argument nullable.
This is needed for CFE integration of field type promotion, since it
allows the CFE to call propertyGet in circumstances where there's no
expression corresponding to the property get, such as during an
invocation of a field that's been parsed as a method call.

Change-Id: I1856705c080315e87e283af217be331021ef8aee
Bug: https://github.com/dart-lang/language/issues/2020
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/260452
Commit-Queue: Paul Berry <paulberry@google.com>
Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
2022-09-22 17:30:29 +00:00
..
benchmarks
lib Flow analysis: use a callback to check if a property is promotable. 2022-09-22 13:09:07 +00:00
outline_extraction_testcases [CFE] Remove many uses of .packages files in tests 2022-06-22 07:34:49 +00:00
parser_testcases [parser] Empty record types, record types with 1 element 2022-08-30 11:04:10 +00:00
test Flow analysis: make propertyGet's wholeExpression argument nullable. 2022-09-22 17:30:29 +00:00
testcases [cfe] Handle structurally constant record literals 2022-09-21 14:19:16 +00:00
tool [CFE] Duplicate code finder experiment take #1 2022-09-16 08:56:50 +00:00
analysis_options.yaml
analysis_options_no_lints.yaml
error_recovery.yaml
LICENSE
messages.status [pkg:js] Add type/conformance checking for createStaticInteropMock 2022-09-16 20:13:30 +00:00
messages.yaml [pkg:js] Add type/conformance checking for createStaticInteropMock 2022-09-16 20:13:30 +00:00
OWNERS
PRESUBMIT.py
pubspec.yaml [pkg] prefer 'any' deps for package dev dependencies 2022-05-27 01:34:59 +00:00
README.md
testing.json [cfe] Remove language version from inference testcases 2022-07-08 12:52:19 +00:00
testing_with_lints.json

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 dart analyze command-line tool to analyze their Dart code.

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

Note: A previous version of this package was published on pub.dev. It has now been marked DISCONTINUED as it is not intended for direct consumption, as per the notes above.